video/export-platforms

Platform Export — generate platform-specific video exports with metadata.

Category: video
Source: workflows/video/export_platforms.py

Input Schema

Field	Type	Default	Description
`composed_path`	`object`	—
`hook`	`object`	—
`media_path`	`object`	—
`output_path`	`object`	—
`platforms`	`any[]`	—
`regenerate`	`object`	—	When set, this run is a regeneration. Workflows may read `direction` / `keep` / `extra_instructions` to modulate prompts; the engine persists `parent_run_id` and `parent_variant_index` as run lineage columns.
`title`	`string`	`""`
`topic`	`object`	—
`variants`	`integer`	`1`	Number of independent variant executions (1–10). When > 1, the engine runs the workflow N times with different sampling, producing N outputs.

Output Schema

No schema defined.

Task Pipeline

prepare_export → resize_for_platforms → generate_platform_metadata → format_exports

Task	Description
`prepare_export`	Validate input and determine target platforms.
`resize_for_platforms`	Generate resized video variants for each target platform.
`generate_platform_metadata`	Generate platform-specific metadata (titles, descriptions, hashtags) via LLM.
`format_exports`	Assemble the final export output.

Run-spec example

Save the YAML below as my-run.yaml, edit the values, and run with the CLI or POST it to the API. Required fields are uncommented; optional knobs are documented above the input: block — copy any line under input: and uncomment to set.

workflow: video/export-platforms

# Optional fields — copy any line(s) under `input:` and uncomment to set:
#   composed_path: null
#
#   hook: null
#
#   media_path: null
#
#   output_path: null
#
#   platforms: []
#
#   title: ""
#
#   topic: null
#

input: {}

Run it locally:

fab-workflow --from-file my-run.yaml

Or submit over the wire — the same file is the request body:

curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=video/export-platforms' \
  -H 'Authorization: Bearer fab_xxx' \
  -H 'content-type: application/yaml' \
  --data-binary @my-run.yaml

Every workflow also accepts the universal WorkflowInput fields — variants (1–10 fan-out) and regenerate (creative-direction hints with run lineage). See Run-specs (YAML / TOML / JSON) for the full top-level shape (metadata, priority, bundle, parent, etc.).

Warnings

Last user task format_exports has no Pydantic return type — workflow output schema is null. Declare a WorkflowOutput subclass and pass it to Flow(output=…) for a strict contract.