Workflows

Steps run in one order: measure, check, act, notify. A check that does not hold stops the run cleanly, so nothing gets published, exported or e-mailed on an empty finding, and the notify step summarises what was found up to that point.

No. Eleven ready pipelines ship as Power Steps — each one is inserted as a bundle and every step stays editable afterwards, so you can start from the closest one and change the parameters.

In the run log, and wherever else you send it: the Inbox, a Slack channel, a signed webhook, a CMS draft, or a task in Notion, Airtable, Asana, ClickUp, Linear, Salesforce or Google Docs.

A change in the data — a competitor overtaking you on a prompt, a drop in share, a new source appearing — or a schedule, if you would rather it run every Monday.

Only if you tell it to. Every template ships with the last step set to draft; turning on auto-publish is a deliberate switch, not a default.

Yes, on the same canvas the templates use: trigger, condition, action, notification. The templates are just starting points somebody already wired.

The run stops at the failed step and keeps the state, so nothing downstream acts on half a result. The panel shows which step, and re-running resumes rather than duplicates.

As many as you have; they queue rather than collide. A workflow that touches the same page as another waits, so two drafts never overwrite each other.

Email, Slack or a webhook. The notification carries the reason it fired, not just the fact that it did.

To the ones with a write API, yes — as a draft by default. For everything else it produces the same output in a paste-ready form.