Help Center

Automation steps: what an automation can do

An automation's steps are the work it does after the trigger fires. The AI builder chooses and sets up the steps from your description, and each one appears as a card on the flow map.

The kinds of step

Each card carries a small badge that tells you its kind at a glance, such as Email, If, Loop or App.

How data moves between steps

A step can use the trigger's data and the results of the steps before it. A step that looks up a customer, for example, makes that customer's fields available to the email step after it.

You do not wire this up yourself. Describe what you need ("email the customer on the order") and the AI builder connects the steps.

Changing a step

Click a step to open the assistant with that step referenced, then say what should be different. To add one, click Add step under the last card. You are describing a change, not editing a form, so be specific: "also include the job address in the email" works better than "improve the email".

Saved credentials

If a step needs an API key for an outside service, save the key once instead of pasting it into a conversation.

  1. On the Automations page, click Credentials.
  2. Add a name in capitals with underscores, such as SUPPLIER_API_KEY.
  3. Paste the value and save.

Steps can then use the credential by name. Values are encrypted and cannot be viewed again after saving. You can replace or delete a credential later.

What costs credits

Steps that ask AI to do something use your workspace's AI credits. Steps that only read or write records, send email or branch on a condition do not.