Automations

When this happens, do that — without writing any code.

Automations

When this, do that

Lead routing
When
A new lead comes in
If
Budget is over $5,000
Then
Assign to Sales + email the client

Who can do this

Owners and admins. It needs a Teams plan or above.

Before you start

  • A Teams plan or above. Each plan sets how many workflows you can have and how many times they may run each month.

Step by step

  1. 1

    Start from a recipe

    Open Automations and browse the gallery. Most of what people build first is already there — notify a channel when a task goes overdue, create a task when a proposal is accepted, chase an unpaid invoice.

  2. 2

    Pick the trigger

    Choose what starts it: a task changing status, a proposal accepted, a contract signed, an invoice paid, a lead arriving, a date being reached, or an incoming webhook.

  3. 3

    Add conditions

    Narrow it so it fires when you mean it — only for one client, only above a value, only for a service type. An automation that fires on everything gets switched off within a week.

  4. 4

    Choose the actions

    Create a task or a project, send a notification or an email, assign an owner, update a record, or call a webhook. Actions run in order.

  5. 5

    Test before you arm it

    Run it once against real data and read what it did. Automations are quiet by nature, so a mistake is only obvious when someone notices the damage.

  6. 6

    Turn it on and watch the log

    Enable it, then check the run log for the first few days. Every run records what fired, what matched and what happened.

Worth knowing

  • Name workflows after what they achieve, not what they trigger on. "Chase unpaid invoices" beats "invoice.overdue".
  • Start with notifications. They are impossible to get catastrophically wrong and they teach you what the triggers really do.
  • Runs are capped per month by plan. The log tells you when you are near the limit.

Common questions

What happens if an action fails?

It is retried, and a persistent failure goes to an error queue with the reason rather than disappearing.

Can one automation trigger another?

Yes, and loops are guarded against so a pair of workflows cannot set each other off forever.

Can I call an external service?

Yes, with the webhook action on plans that include it.

Still stuck?

Send us the details and it becomes a tracked ticket with a reference you can follow.

Contact support