Skip to main content
An automation watches for an event, checks conditions, and runs a flow, send an in-app push, wait two hours, send an email, branch on what happened. Instead of exporting a list and sending a batch, you respond the moment a wallet does something.

​
Anatomy of an automation

Every automation has exactly two parts:

A trigger

What starts the flow. For a business preset like Token acquired or Swap completed, you pick your token or contract and the platform fills in the on-chain event for you.

A flow graph

Nodes and edges. Each node is an action, a wait, or a branch. Execution follows the edges from the trigger node.

​
What you can build with

See Triggers and Conditions for the full catalog and Connect to Campaigns for the messaging actions.

​
Lifecycle

An automation is always in one of four states:
Setting the status to active is not enough to make an automation run. The runtime only executes a published version of the flow graph. If you activate without publishing, the automation will match events and create entries, then complete having done nothing.Always finish with Publish. See Create an Automation.

​
Plays vs. blank canvas

Most teams should start from a proven play rather than an empty builder. A play ships with a pre-wired trigger, a working flow, and copy you can edit. Six built-in plays are available to every workspace: Forking a play creates a draft automation you own. The four on-chain plays ship with an empty contract address, fill it in before publishing.
Advanced plays are gated on workspace readiness: indexed wallet count, days of indexing history, and enabled protocol features. If a play reports readyToShip: false, the response lists the setup steps still outstanding.

​
Limits

Active automations are capped only on the entry tier: Archived automations never count. On Pay as you go, once you’re at three, activating another is blocked until you archive one or move to a paid plan.

​
How to think about it

Start with one trigger, one audience rule, and one outcome. Verify that path end to end with a real event before adding branches. A narrow automation that fires correctly is worth more than a wide one nobody trusts.