Lesson 6 of 10 · 5 min

Publish a workflow and what it costs

Publish a workflow so its triggers go live, and work out its real cost from the daily fee plus the AI steps it runs.

What Publish does

Publish saves the current draft as a version and makes it live in this project. Its triggers start. A schedule begins firing at its next time. A webhook starts accepting calls on its production URL. An event trigger starts listening.

The publish dialog shows any problems first. A node with a missing account or an empty required field blocks publishing until you fix it.

Live workflows run as the person who published them. If that person later loses access to the project, the workflow stops and the project is notified.

Editing a live workflow

After you publish, you can keep editing the draft. The live version does not change until you publish again. The Publish button tells you when there are new changes to publish. To stop a workflow, choose Unpublish. Its triggers turn off right away.

What it costs

There are two kinds of charges.

  • A daily fee per live workflow. Each live workflow costs 2 credits a day. Today is charged when you publish. After that, it is charged once each day while the workflow stays live. Publishing the same workflow again on the same day does not charge twice.
  • AI steps as they run. Nodes that use AI, such as Generate static ads, Write social caption, Quality check, or the AI agent, use credits each time they run. They cost the same as making that creative or text by hand.

Every other node is free. Triggers, branching, data steps, HTTP requests, Code, scheduling posts, ad and email operations, and notifications cost nothing per run.

Drafts never pay the daily fee. Test runs never pay it either, though AI steps inside a test run still use credits.

If you run low on credits

If the daily fee cannot be paid, the workflow is unpublished and you get a notification. The editor shows that it is paused for credits. Top up, then publish again.

Fair-use limits

Free steps have daily limits per live workflow:

  • 2,000 executions
  • 30 minutes of Code node time
  • 5,000 HTTP requests

If a workflow hits a limit, new runs wait until the next day (UTC). You are not charged for hitting a limit.

Check the estimate first

The publish dialog shows the daily fee and an estimate of AI credits per run. Multiply that estimate by how often the trigger fires. That is the honest monthly cost, and it is the number to compare against the budgets in the next lesson.

Reference

Keep going