Agents
Workflows
Automate work across your tools: pick a trigger, add steps, test with pretend customers, and publish. Workflows run every time the event happens.
Workflows run a set of steps every time something happens in your business: a new Meta lead, a board item moving to a status, a call ending, a form submission. They reach your team's tools, so a new lead can become an item on your Leads board and a call with a representative in the same minute.

How workflows work
Each workflow has two parts:
- A trigger: the event that starts the workflow.
- Steps: actions and flow steps that run after the trigger fires.
You build workflows on a visual canvas with no code, or describe what you want and Ally builds it.
Workflows run in the background. When a job happens inside a conversation or on a board item and needs fixed steps, use Procedures instead.
Create your first workflow
Test it
Click Test workflow and run a full test or a scenario. See Test a workflow.
Your changes save automatically. After the first publish, edits stay as Unpublished changes until you click Publish changes, so you can work on a live workflow without affecting it.
Or let Ally build it
Ally can also change one field in an existing workflow when you ask, and it runs a simulation after it builds or edits one.
Workflow states
The workflow list shows a dot for each state: green for Live, amber for Off, and hollow for Draft. Filter the list by All, Live, Off, or Draft. In the editor, the toolbar chip shows the on/off switch, the version, and whether there are unpublished changes.
Triggers
A trigger is the event that starts your workflow. Every workflow has exactly one trigger.
Leads, contacts, and conversations
Boards
Board triggers fire on items of the board you pick. See Boards.
New Ticket is listed under Legacy when your workspace has the built-in Tickets board. Use Item created on the Tickets board instead.
Bookings, orders, and schedules
Integrations
Trigger filters and variables
Many triggers have filters that narrow when the workflow fires, such as one form, one agent, or one status.
Every trigger gives you data to use in later steps with the {{variable}} syntax. For example:
- New Order gives
{{orderId}},{{customerName}},{{customerEmail}},{{totalAmount}}, and more. - Form Submitted gives each answer as
{{fields.<name>}}, the person's own words for a choice as{{answers.<name>}}, and{{declined}}for questions they chose not to answer. - New Appointment gives
{{attendeeName}},{{attendeeEmail}},{{startTime}},{{serviceName}}, and more. - Facebook Lead gives
{{contactId}}when the lead is saved as a contact.
Actions
Actions are the steps that do the work. Each one can use data from the trigger and from earlier steps.
Messaging
Template fields you leave empty fill themselves from the incoming data with the same name, then from the field's default. The editor marks them (automatic). Promotional emails respect opt-outs and include an unsubscribe footer.
Outbound calls
Connect Call reports how the call ended in {{customer_outcome}}: connected, no_answer, busy, unreachable, voicemail, declined, no_response, teammate_hung_up, customer_hung_up, or dial_failed. It waits for the voicemail check before the next step, so you can branch on voicemail. Teammate lines can include a desk extension. If a Connect Call already reached the customer in the last 12 hours, the step is skipped. See Human Handoff.
Under After sending, choose Move on, Wait for tap, or Wait for reply, and how long to wait (24 hours by default). A tap gives {{button_payload}} and {{button_title}} for a Switch. A reply gives {{reply_text}}, {{reply_email}}, and {{reply_phone}}.
AI
Timing and approvals
Wait until something happens waits for an event on the same contact, item, or conversation, such as Contact Replied, with a Give up after limit. Turn on Stop the workflow if it happens to build "send, wait, follow up" sequences: if the customer replies, the follow-up never sends.
Boards
Data
Formatter, research, and HTTP
Integrations
Flow steps
Flow steps control which path a run takes. Add them from the + picker.
A condition compares a Field to a Value with an operator like equals, contains, or greater than.
Variables
Use data from the trigger and from earlier steps anywhere in a later step: message text, AI prompts, HTTP payloads, and conditions. The variable picker lists what each step gives you. Common outputs:
AI Transform and Ask Agent let you name their output, so you choose the variable.
Test a workflow
Click Test workflow in the toolbar to open the test sheet.
Scenarios can include simulated events, like a contact replying, to prove that a Wait until something happens path works.
Checks at publish
Publish stops you when something would fail in production:
- A template that is missing, paused, or not approved, or a required template field with no value.
- Send template on a board trigger with no recipient.
- Reply to Comment or Send DM without an Instagram trigger.
It warns, without blocking, when a form answer is mapped into a board field it may not fit, such as a text answer into a phone field.
Run history
Every time a workflow runs, it creates a run. Open run history in the editor to see each run's status, when it was triggered, and the trigger data.
Example workflows
New Meta lead to a call in minutes
Trigger: Facebook Lead, with Save the lead as a contact on
- Create item on the Leads board.
- Connect Call to your sales team.
- Switch on
{{customer_outcome}}: ifconnected, Move to status "Contacted". Otherwise, Send template with a follow-up SMS.
Follow up until they reply
Trigger: Item enters status "Quote sent"
- Wait 2 days, until Contact Replied, with Stop the workflow if it happens on.
- Send template: a short check-in email.
- Wait 3 more days, the same way.
- Notify someone: tell the item owner to call.
Unresolved conversations become work
Trigger: Conversation ended, outcome Unresolved or Escalated
- Create item on the Support board with the summary.
- Ask Ally to work on it so the owner gets a draft reply to review.
High-value order approval
Trigger: New Order, with a condition on {{totalAmount}} greater than 500
- Wait for Approval: ask the owner to review the order.
- Switch on
{{approval_status}}: ifapproved, Change Order Status to confirmed. Ifrejected, change it to cancelled and email the customer.
Tips
- Start small. A trigger and one action, then add steps.
- Test with scenarios. A pretend customer shows the path without sending anything.
- Publish changes on purpose. Edits wait as Unpublished changes until you publish.
- Check run history. It shows exactly where a run failed.
FAQ
How many workflows can I have?
There's no limit on the number of workflows per workspace.
Can I turn a workflow off without deleting it?
Yes. Switch it off in the toolbar chip. It moves to Off and keeps its settings.
What happens if a step fails?
The run stops at that step and is marked Failed. Other runs and workflows aren't affected. Add a Condition or Switch to handle expected cases, like no answer on a call.
How is a workflow different from a procedure?
A workflow runs in the background on an event, with no conversation. A procedure is steps an agent follows in a conversation or on a board item.
Can workflows call external APIs?
Yes. HTTP Request calls any URL with a custom method, headers, and body. For incoming events, use Custom Connections.