Automation and AI

Workflow actions

Every step a workflow can take, what each one changes, the permission it needs, and how workflows are stopped from looping.

View as Markdown

Add steps with Add a step. Steps are grouped as Messages, Tasks and people, Flow and AI. Which steps you're offered depends on the trigger: a step that needs a client only shows on triggers that carry one, and a step you don't have permission for is hidden.

Messages

  • Send email — to the lead, the client, the assigned teammate, or someone else. Choose the mailbox it sends from under From; replies arrive in that mailbox in Inbox. In Settings, Sends from sets the mailbox on every email step at once.
  • Send text message — to the same kinds of recipients. Only text people who agreed to get texts from you; clients who opted out are skipped. Text steps need a plan that includes them.
  • Only send during business hours — an option on Send email and Send text message. A send that falls outside the business hours set in Inbox settings is held until the next opening, and later steps count from that time. With no hours set it does nothing, and the step shows Set business hours. A workflow with an AI decision sends at any time.
  • Reply to sender — replies on the same channel and in the same conversation as the incoming message. It's only in workflows with an AI decision. In a workflow without one, use Email the sender or Text the sender instead: a new message to the sender, from the mailbox you choose.
  • Notify teammates — an in-app and push notification. Choose All teammates, Chosen teammates, or the Assigned teammate, whoever is assigned when the step runs.

On an incoming-message trigger, The client as a recipient is the sender. For a text message that came from an email conversation (or the other way round), it goes to the matching client's phone (or email). If the sender isn't a client, the step is skipped.

Tasks and people

  • Create task — a task on a board, with its title, description, priority, due date and assignees. It's linked to the client, the lead and the project of the record that started the workflow.
  • Create reminder — a reminder for a teammate, Right away or later.
  • Assign to teammate — hands a new lead to One person or rotates it between several (Round robin). It shows Next up, and you can drag teammates to reorder the rotation. Only people who can see Requests can be picked. It's offered on the New lead trigger.
    • Also move their booked call — moves the lead's upcoming booked calls to the new teammate, when they're free at that time. If they're busy, or their calendar can't be read at that moment, the call stays with its host and the run says so. Next up in the rotation moves on when you publish. The client keeps their invite and meeting link.

Client and lead records

These change a record, and they need permission (see the table).

  • Move client to stage — moves the client to a stage you choose, even if one of your stage rules would move them elsewhere. Workflows that start on a stage change will run.
  • Update a client field — sets a field on the client, or clears it (Clear the field instead).
  • Add or remove tag — under Tags go on, choose the client (or the lead, on lead triggers). On Lead converted to client it tags the lead, not the client it became.
  • Set lead status — marks the lead new, reviewed or archived. An archived lead is left as it is; restore it in Requests to change its status.
  • Convert lead to client — creates the client, or links an existing client with the same email or phone, and marks the lead converted. Client created workflows will run. Offered on New lead, Lead status changed and Lead assigned.

Documents

  • Convert proposal to invoice — offered on Proposal accepted. The invoice gets the next invoice number and a payment link.
  • Send invoice — offered on invoice triggers. Sends the invoice with its PDF and payment link. Leave the message empty to use your invoice email template.
  • Send contract — sends a contract from a Template. A template with roles you fill in by hand can't be sent by a workflow. It uses a contract from your plan, or Tokens when there are none left.
  • Remind contract signers — offered on contract triggers where someone can still sign. Emails everyone who was sent the contract and hasn't signed. Anyone reminded in the last 24 hours is skipped.

Flow

  • Stop the workflow — ends the run when a condition matches, so nothing after it runs. The run shows Stopped. Choose Stop when, then All rules match or Any rule matches. Common rules gives you ready-made ones, such as "The invoice is paid" or "The client has accepted or declined". Stop steps also work in workflows with an AI decision.
  • Check a condition — splits the flow into Yes and No on the record's own fields, with no AI. Steps on Then run for every record. See Build a workflow.
  • Wait — Wait for a time, or Wait until a date on the record, for up to 365 days in all. See Waits.

Permissions

A step that changes a record runs with the rights of the person who last published the workflow. If they lose the permission, the step fails with a message saying so; give the permission back, or have someone who has it publish the workflow again. In the editor, you need the permission yourself to change one of these steps.

StepYou need permission to
Add or remove tag (client)edit clients
Add or remove tag (lead)edit leads
Move client to stage, Update a client fieldedit clients
Set lead statusedit leads (archive leads, to archive)
Convert lead to clientconvert leads and add clients
Convert proposal to invoiceconvert proposals to invoices
Send invoicesend invoices and send emails
Send contractcreate contracts, send contracts and view contracts
Remind contract signerssend contracts

Loop protection

Workflows can trigger each other: one moves a client to a stage, and another starts on that stage change. To stop this running away:

  • A workflow never starts itself from a change it made.
  • If workflows change the same record 3 times in 10 minutes, the 4th run stops at that step and logs "Loop stopped: workflows changed this client 3 times in 10 minutes."

One run that changes the same record several times counts once.

Next steps

Return to Workflows.

Was this article useful?

Your answer helps us decide what to clarify next.