Triggers & Events

Loops use one of two trigger types: Event-based or Scheduled. An event Loop is tied to a Connection and a Trigger event, so Loops that start from GitHub, Slack or a Channel are all event Loops.

Connected services

Use when: something that happens in one of your services should start the agent.

Events come from these Integrations: GitHub, Slack, Jira, Confluence, Notion, Google Calendar and ServiceNow. They are your team’s own services, so their Loops need an Internal agent.

A message from a customer on Telegram, SMS or WhatsApp (through Twilio), your website chat or the Email channel is an event too. Those Loops need a Customer-facing agent, and Add channel in the agent’s Channels section creates the Loop for you.

Some connections need their webhook set up before a Loop can use them. The Connection list in the Loop dialog says how many still need it; set them up from the Integration’s page in Integrations. Each connection has its own webhook address on https://webhooks.auteryn.ai; copy it from there rather than typing it.

GitHub Events

Create an event Loop with a GitHub connection. The trigger events are:

• Issue Opened
• Issue Closed
• Pull Request Opened
• Pull Request Merged
• Code Pushed

Setup:

1. Connect GitHub under Integrations
2. Choose Create Loop, then Event-based
3. Select the GitHub connection and trigger event
4. Pick an Internal agent

Slack Message

Create an event Loop with a Slack connection:

1. Connect Slack under Integrations
2. Choose Create Loop, then Event-based → your Slack connection → Direct Message, Bot Mentioned, Channel Message or Reaction Added
3. Pick an Internal agent

Requires an Internal agent (Slack workspace events are internal-category).

Email

Connect the Email channel under Integrations. It gives you an Auteryn address.

1. Forward your support inbox to that address
2. Attach the channel to a Customer-facing agent: in the agent’s Channels section choose Add channel, or create an event Loop with the Email Received event
3. Each email that arrives runs the agent, and it replies by email

Scheduled

Run your agent once or on a timetable. See Scheduling →. Requires an Internal agent.

Manual

Choose Run on a scheduled Loop that is on to start a run now. Event Loops have no Run button: they run when their event arrives.

---

Event format

The agent receives a short text summary of the event, not the raw payload, so you do not configure template variables like {{event.raw}}.

Example — a GitHub issue opened:

GitHub Issue Event: opened
Repository: acme/app
Issue #42: Login button not responding on mobile
Body: Steps to reproduce...
Author: jdoe
URL: https://github.com/acme/app/issues/42

The agent gets a message on a Channel as the sender’s words, with who sent them.