Workflows turn a validated Job definition into a reusable product asset. They are useful for signed conversion URLs, MCP agents, Zapier and repeated cloud-to-cloud processing.
Immutable versions
Updating a Workflow creates a new version. Existing Jobs and signed links continue to reference the exact version they were created against. Store the version identifier alongside your own deployment configuration when exact reproducibility matters.
Variables
Define a schema for safe caller-supplied values such as a source URL or destination key rather than allowing arbitrary DAG mutation. Validate types, limits and allowed hosts up front so a reusable workflow cannot be turned into an unrestricted execution surface.
Run a Workflow
Validate first when building dynamically, then run the saved Workflow with a variable map and optional client reference metadata. Treat the returned Job ID as the durable execution handle and use webhooks for completion.
Production controls
Pin signed URLs and external automations to a specific Workflow version, use idempotency around run creation, and roll forward by creating a new version rather than mutating behavior in place. Retire old versions only after callers and signed links have moved.