Current workflow capabilities
How to use workflows
- Open Dashboard > Workflows.
- Create a workflow.
- Choose conversion, compression, storage, and webhook steps.
- Run a test to validate the flow.
- Save the workflow. Live runs are processed asynchronously.
Production guidance
Live workflow runs return immediately with a run ID and continue in the worker queue. For programmatic batch workloads, usePOST /api/jobs with webhooks when you need idempotency keys, archive delivery, and direct API-level control.
Workflow API
Workflows can be authored and executed without ever opening the dashboard. The endpoints accept either a Convertly dashboard session or a Bearer-token API key. WordPress site-scoped keys are not allowed. Workflows belong to the workspace and remain available to its owners if the billing owner changes. Full request and response shapes are in the Workflows API reference.
The
POST /api/workflows payload mirrors the dashboard builder’s schema:
AI agents (MCP)
The Convertly MCP server exposes the same workflow surface to Claude, Cursor, Codex, and any MCP-compatible client. Once@convertly-sh/mcp is connected, an agent can be told things like “create a workflow that converts incoming images to AVIF, compresses them, and saves the output to my main storage”. The agent will pick the right tool, build the definition, and confirm with you before destructive actions.
See MCP for AI agents for client setup.
Step types
Workflows are built from typed nodes. Every node has akind and an optional config bag. The engine’s per-node executor reads whichever config keys it cares about and ignores the rest.
The following kinds round-trip through the API and the dashboard but don’t have an executor wired yet:
transform, watermark, trim, thumbnail, poster_frame, storyboard, extract_audio, gif, image_to_pdf, pdf_preview, inspect. They’ll execute as soon as their executors land. The schema is stable now so you can author against it.
Related docs
Async jobs
Queue larger media workloads and track progress.