Starting an agent automatically from an app event Guide

Most agents run when you ask them to. But some of your best workflows happen while you're away from your desk — a new order arrives, a deal moves stages, a customer texts in. When a connected app supports triggers, one of those events can start an agent for you automatically, with no one at the keyboard.

What a trigger is

Every app you connect exposes actions — things your assistant and agents can do inside that app. Some apps also expose triggers: events that happen in the app and can kick off an agent on their own.

Actions are what an agent does. A trigger is what makes an agent start. If you want an agent to run without you prompting it, you need an app with a trigger.

Common examples of trigger events include:

• A new e-commerce order is placed
• A CRM record is created or changes
• A bank or payments event occurs
• An inbound SMS or phone call comes in

Not every app has triggers. Many apps offer actions only. If an app has no triggers, you can still use it inside an agent's steps — it just can't be the thing that starts the run.

Before you begin

Two things need to be in place first:

1. The app is connected. Open the Integrations hub and connect the app whose events you want to react to. Make sure the actions your agent will need are enabled for that connection.
2. The agent exists. You'll need an agent ready to receive the event, with clear instructions for what to do when it runs.

Check whether an app can trigger an agent

Before you build anything, confirm the app actually offers the event you have in mind.

1. Go to the Integrations hub and open the app's card.
2. Open its capabilities view, which lists everything the app can do.
3. Look for the Triggers section, separate from Actions. You can search within the list to find a specific event.

If the event you want appears under Triggers, the app can start an agent automatically. If you only see Actions, that app can't be the starting point — though it can still do work inside a running agent.

Point an agent at the event

Once you've confirmed the trigger exists, connect it to your agent so the event starts a run.

1. Open the agent you want the event to start.
2. Choose the connected app and the specific trigger event that should launch it.
3. Write clear instructions for what the agent should do each time the event fires — the agent receives the event's details and works from them.
4. Save the agent so the trigger is live.

From then on, whenever that event happens in the connected app, the agent starts on its own and carries out the instructions you gave it.

Give the agent the right actions

An automatically started agent can only do what its connected apps allow. If the agent needs to reply, update a record, or send a message, make sure those actions are enabled on the relevant connection. If an agent reports that an action isn't enabled, open that connection's actions and turn the needed one on.

Test it end to end

Before you rely on the automation, confirm the whole path works.

1. Create the real event in the connected app — for example, place a test order or send an inbound message.
2. Check your agent's activity to confirm a run started and used the event's details.
3. Review what the agent did and adjust its instructions if anything was off.

Tip: Start with a narrow, low-risk trigger and read the first few runs closely. Once you trust the behavior, widen it or add more actions.

Troubleshooting

The agent didn't start

Confirm the app is still connected and the specific trigger is selected on the agent. If a connection was interrupted, reconnect it from the Integrations hub and try the event again.

The agent started but couldn't finish a step

The agent likely needs an action that isn't enabled. Open the relevant connection, review its enabled actions, and turn on the one the agent asked for.

The app has no trigger

Many apps offer actions only. If the app you want can't trigger an agent, consider whether a different connected app in the same workflow exposes an event you can start from instead.