Workflows
A canvas for multi-step automation: LLM calls, search, logic and publishing, run on demand or on a cron.
On this page
What a workflow is
A chain of steps on a canvas. Each step takes the output of the ones before it, so a workflow can research a keyword, draft from the result, check it, and publish — without anyone re-pasting anything between tools.
Building one
Start from Browse templates or New workflow. The editor has an Ask AI dialog that rebuilds the canvas from a description, immutable versions you can restore, and a run drawer showing every step's input, output and duration.
The step catalogue
Thirty-three step kinds across triggers, channels, integrations, logic and output. The ones people reach for most: LLM call, Web search, Web scrape, Perplexity research, Reddit search, HTTP request, Filter / Extract, Branch (if/else), Loop (for each), Code, Human review, Notify, CMS publish, Google Doc, Stage rows in grid, Read rows from grid, AI citation check, Competitor overlap, Citation intel, GSC metrics and Workspace LLM gaps.
Connections
Credentials live once as connections and any step can use them: the 35 apps in the connector catalogue, the publish targets, a Slack incoming webhook for the Notify step, and your own model keys. A Connector step reaches any operation a catalogued app declares.
Templates
Twenty-two, grouped as Content & AEO · Research & analysis · Monitoring · Outreach · Integrations & data: content briefs and article drafts, FAQ and schema generators, keyword clustering and SERP analysis, daily citation digests, competitor watchers, content refresh from GSC decay, a Reddit thread responder, and more. A cloned template is a Draft until you set it Active.
What a run costs
Control flow is free — triggers, branches, filters, code, notify, loops, human review. A single outbound request is 1 task; fetch- and search-shaped steps are 3; LLM-shaped steps are 5; citation fan-outs are 10. Model tier changes an LLM step's price — economy 2, standard 5, premium 10 — and running on your own key is a flat 2.
Scheduling
Scheduling is a single field, Schedule (cron, optional), taking a standard five-field cron — 0 9 * * * is daily at 09:00 UTC. Leave it empty for on-demand only. A scheduled workflow fires only while its status is Active.
Nothing notifies you when a scheduled run finishes or fails. If you want to hear about it, add a Notify step — in-app, or to a Slack incoming webhook.
Runs, debugging and versions
Every run is kept with its per-step detail. You can re-run a single failed step against that run's upstream outputs instead of restarting, test a step from the editor, restore an earlier version, and export or import a workflow as JSON.