API Reference / Create a workflow
Create a workflow
Compose a recurring workflow from a schedule in plain words and a list of steps.
curl -X POST -H "Authorization: Bearer $REVNU_API_TOKEN" \
-H "content-type: application/json" \
-d '{"name":"EU HPC daily","scheduleText":"every weekday at 09:00 Europe/London","steps":[{"title":"Find five leads","details":["EU operators of owned GPU or HPC capacity","Five per day, skip anything on the block list"]},{"title":"Draft and deliver","details":["One LinkedIn draft per lead, sourced hook, no pitch"]}],"deliverTo":"web"}' \
https://revnu.com/api/v1/workflowsBody
name (up to 120 characters), scheduleText (plain words, up to 200 characters), steps (1 to 25). A step is { title, details?, gate?, id? }: details is up to 8 lines, gate: { on: true, label? } means the step waits for a human ok before it acts. Optional description (240 characters) and deliverTo, one of the account's connected destinations. Unknown fields are a 400.
Response
{ "workflow": { workflowId, status, version, scheduleText, scheduleEcho, scheduleError, nextRunAt, steps, url, … } }, status 201. The workflow is live. The schedule resolves after the write: read it back for scheduleEcho and nextRunAt, or scheduleError when the words could not be understood.
Agents: this page is also markdown at /docs/workflow-create.md, answers Accept: text/markdown, and is listed in /docs/llms.txt.
Frequently Asked Questions
In a step's `details`, as words: "five per day". The agent honours it on every run, and in practice holds it exactly, but it is an instruction the agent reads, not a ceiling we enforce. There is no numeric volume, budget or end-date field.