Skip to main content
Version: v2.0

Trigger an automation from an app

An event trigger starts an agent run when something happens in an app you connected, with nobody in the chat. This page sets one up. Prepare the agent first with Create an automation, because the run cannot ask you anything once it starts.

Connect the app first​

An event trigger fires from an app this project is connected to. To connect one, go to Sidebar > Settings > Triggers and click + Connect on the Connections section. Connected apps are listed there with their Integration, Name, Slug, Status, and Created at.

The trigger picker shows your connections in its left rail, under YOUR CONNECTIONS, and each app card has a + Connect another account button for adding a second account.

Commit before you subscribe​

An event trigger runs one pinned variant and revision. Commit the agent first, so the trigger can pin the version you want it to run. In the Configuration header, click Commit, keep New version, and confirm.

Pick the app and the event​

Two ways in, both opening the same picker.

From the agent. Sidebar > Agents > <agent name>, set Playground mode to Build, scroll the Configuration column to the Triggers heading, and click Add subscription on the Subscriptions section.

From project settings. Sidebar > Settings > Triggers, then + Subscribe on the Event triggers section.

The Choose a trigger dialog opens with your connections in the left rail, a Search apps… box, and the ALL APPS grid.

Click the app. Its card shows the connection, then CHOOSE AN EVENT with a Search events box and the events that app can fire. Click the event you want.

Fill in the trigger​

Picking an event opens the New trigger dialog.

1. Name​

Type a Trigger name. It is what identifies this trigger in the Event triggers table.

2. When this happens​

The event you chose is shown here with the app it comes from. Below it, Event filters narrows which occurrences start a run. The fields depend on the event. A GitHub event asks for Owner and Repo, and for an Interval in minutes, which is how often the event is checked.

Fill in every field marked with an asterisk.

3. Which version runs?​

Choose Pinned, which runs one exact variant and revision, then select the variant. Every run of this trigger uses that revision.

4. What the agent gets​

Write the message the agent receives when the event fires. The left column, EVENT FIELDS, lists the fields the event carries. Click a field to drop its live value into the message, so each run tells the agent which issue, branch, or record it is about.

To see real values in that column, use Test event.

Test it, then switch it on​

Click Run in playground in the footer to run the agent with the message you built. Once the run does what you want, set the Active toggle and click Create.

To create the trigger without arming it, leave Active off.