An agent can start on its own when something happens in your workspace (a chat closes, a lead form arrives, an order ships), when your own system calls a webhook, or on a schedule.
An agent can start on its own when something happens in your workspace (a chat closes, a lead form arrives, an order ships), when your own system calls a webhook, or on a schedule. Every new trigger starts switched off and in test mode, so you can check it before it acts on real customers.
Where to find it
AI → Agent Studio → Automations. Each agent's triggers show their state there and in the agent's editor.
Before you start
Your plan includes AI agents (ai_agent). Some events need more features (see the table).
The agent is published. Publishing registers its triggers.
Kinds of trigger
Trigger
Starts the agent when…
Customer message
A customer writes on the agent's channels
Event
Something happens in your workspace (list below)
Webhook
Your own system sends a signed request to the trigger's address
Schedule
At set times (for staff tasks such as a morning digest)
Hand-over
A chatbot or another agent passes the conversation
Events you can use
Group
Events
Needs
Conversations
Conversation started, Conversation closed, Conversation reopened, Conversation assigned, Conversation unassigned, Tag added to / removed from a conversation, Conversation episode opened, Internal note added, Staff member mentioned, Reminder due, Messaging window closing soon, Conversation went quiet
—
Contacts
Contact created, Contact field changed, Contact added to / removed from a group, Contact opted out or in (DND)
Order placed, Order paid online, Cash-on-delivery order placed, Order shipped, Order delivered, Order cancelled, Order refunded
ecommerce
SLA
SLA about to breach, SLA breached, SLA breach withdrawn / resolved / acknowledged, Acknowledged breach reopened, SLA met
sla
Messaging health (staff only)
Message template status changed, Message template quality changed, WhatsApp number quality changed, WhatsApp account alert, WhatsApp Flow status changed
—
"Conversation went quiet" can mean the customer is waiting for you, you are waiting for the customer, or nobody has written. The shortest wait is 15 minutes.
There is no "message received" event. A normal customer message reaches an agent through its channel.
Steps
Turn on an event trigger
Publish the agent
Publishing registers the trigger. It shows Off ("Not listening. Test it with the sample, then go live.").
Click Test it with a sample event
You can also pick …or a recent real event. The test always uses your draft. Check what the agent would have done in the result below the buttons.
Click Watch real events in test mode
The trigger shows Test mode: it listens to real events but only simulates. Nothing real changes.
Click Go live…, read the list in Go live with this automation? and click Go live
The trigger shows Live and acts on real events. You can click Back to test mode or Turn off at any time.
Use a webhook trigger
Publish the agent
The webhook trigger gets its own address, switched off and in test mode.
Open the trigger in the agent's editor and copy its address and signing secret
The signing secret is shown only once. Store it in the calling system right away. For providers that sign their own webhooks (for example Shopify or Stripe), you paste the provider's signing secret instead.
Send a test request and check the result
Switch the trigger to live
This asks you to confirm.
Use a simple automation instead
If a webhook from your system only needs to send one approved WhatsApp template or start a chatbot, a simple automation is enough. You test it with a dry run, then activate it. Meta lead ads that send a template or start a chatbot are set up on a chatbot webhook (Chatbot → Webhooks, with Meta Lead Ad on). See Facebook lead ads.
Limits and plans
Event triggers depend on your plan (ai_agent) plus the event's feature (sla, ecommerce, lead ads). Check Billing → Current Plan.
A trigger on an event your plan lacks cannot be published. If your plan loses a feature later, those events are ignored.
By default, a trigger fires at most 12 times per conversation per hour. Agents send at most 3 automated texts per conversation per day.
Unattended AI work has a daily budget that resets at midnight UTC.
Good to know
An event trigger can filter events (up to 20 conditions) and wait for a quiet period before it fires.
By default an agent ignores events caused by its own actions, so it does not loop.
Workspace events such as template or number quality changes go to staff, not customers.
Agent Studio → Settings → Automation safety has Stop all automations, a kill switch. Only a person can turn it on or off. Work due while it is on is cancelled, not queued: it does not run later.
The state "Mixed" means an agent's triggers are not all in the same state.
Do it with Copilot
Do it with Copilot
Which events can start an agent in my workspace?
Do it with Copilot
When a conversation closes, send the customer a short AI summary.
The Copilot starts from the closest recipe.
Do it with Copilot
Show the last deliveries for the lead form trigger and why any were ignored.
Do it with Copilot
Switch my installed order-shipped automation to live.
Going live asks you to confirm. The Copilot can switch installed automations and webhook triggers. Event triggers you added to your own agent are switched in Agent Studio.