On a clock or a feed
Publish on a rhythm, or whenever new content appears.
- On a schedule
- New item in an RSS feed
- Webhook is called
Pick a trigger, add a few steps and switch it on. Workflows post to your channels, publish articles to your site and answer comments, DMs and reviews while you get on with your day.
Every workflow is one trigger with steps under it. A signal comes in, each step runs in order, and each one can use what the steps above it made.
A comment, a review, a new article, a schedule or a call to your webhook starts the run.
Write, design, filter, wait, post, publish or reply, one step after another.
A new workflow is a draft until you set it live, and Pause stops it straight away.
Your calendar, your feeds, your sites and the people talking to you. Point the trigger at exactly what it should watch.
Publish on a rhythm, or whenever new content appears.
A row reaches a status, or a post is published.
A comment, a DM, a mention or a review.
Start a run when someone subscribes or is given a tag.
Built with the email release, so a subscriber can start a run the day they join.
Add up to ten steps under the trigger. Each one picks up what the steps above it made and passes its own work down.
Writes a caption, an article or a reply from your prompt.
Makes an image from a prompt to go with it.
Makes a short video from a prompt. Coming soon.
Writes the same post in another language, from the same brief.
One step per channel, so a run says exactly which one failed.
To WordPress, Webflow or your own endpoint.
Sends one of your emails to the contact. Coming soon.
Takes turns through the products you imported, one per run.
Answers the comment, review or message that started the run.
Keeps spam off your Instagram and Facebook posts.
Continues only when AI rates the text as negative, spam or what you describe.
Follows back new followers on the channels that allow it.
Continues only when the conditions you set are met.
Waits a while before the next step.
Calls any url to fetch data or send it to your own systems.
Combines, shortens, cleans up or changes the case of text.

A generate step writes once. Every place it goes is its own step with its own account, run one after the other: your channels, your blog, and soon your email list.
Drop a value from any earlier step into a prompt: the article title, the comment text, a review's stars. Then test each step against what the one above it really produced.
Summarize {{trigger.title}} in 2 sentences for a LinkedIn audience, then add 3 hashtags.
From the trigger{{2.text}}However you start, the workflow opens in the builder with its steps in place, ready for you to fill in and switch on.
Type what should happen and when, and AI builds the workflow with its steps set.
Search the ready-made workflows, or browse them by section.
An empty workflow in the builder, for you to add steps to.
When someone leaves a one-star Google review, post it to Telegram and draft a reply.
Each workflow keeps a history of its runs: when it started, how long it took, how it ended and, when it stopped, why.
Running now.
Finished with no error.
Stopped on an error, and the run says which step.
A filter stopped it on purpose.
Pause stops the runs straight away and keeps the history, so you can see what happened.
Started 09:41. Second step of three.
Four steps finished in 6.2 seconds.
Filter 01 said no: the comment had no keyword.
Post to Instagram stopped the run: reconnect the channel, then retry from that step.
Four steps finished in 6.2 seconds.
Exited is not a failure. A filter that lets one keyword through exits on every comment without it, which is the filter doing its job.
Open View runs first. No runs, Exited or Failed: each one points at a different answer.
“All errors must be resolved before toggling the workflow on or off”
New workflows start inactive, and a paused one stays that way until you set it live again.
A red count in the header means a step still needs something. Set live stays greyed out until it reaches zero.
The most common answer. Some triggers are checked on a timer rather than straight away.
A run marked Exited met a filter that said no. Check its keywords against what arrived.
Over MCP, Claude or ChatGPT can list your workflows, switch them on and off, and start a run on demand.
A schedule, a new item in an RSS feed, a call to the workflow's webhook, a new post on your site, or someone talking to you: a comment, DM or mention on Instagram or Facebook, a Google review, a reply on Threads, X or Telegram, or a WordPress comment.
Only once you set it live. A new workflow stays a draft, and you can test it a step at a time, so you read the caption and see the image before anybody else does.
Not yet. Send email and the contact triggers are in development. Today workflows post to your channels, publish articles to your site and answer comments, DMs and reviews.
You write the prompt and drop in values from the steps above: the article title, the comment text, a review's stars. Generate text hands back the words, Generate image hands back a picture, and the steps after them use both.
Point the trigger at exactly what it should watch: one account, one feed, or a row that reaches the status you choose. Then add a Filter step, or an AI filter that only lets through what AI rates as negative, spam or what you describe.
No. A workflow runs one path, top to bottom. A filter can stop a run that should not continue, and a second workflow can handle the other case.
Instagram, Facebook and Telegram start a run straight away. Google reviews, WordPress, Webflow and TikTok are checked every 5 minutes, and RSS feeds every 1 to 2 hours.
Build your first workflow in a couple of minutes, then let it run.