Create a Loop
Auteryn supports two kinds of Loop: event-based (something happens in a connected service such as GitHub, Slack or Jira, or a message arrives on a Channel) and scheduled (once, or on a timetable).
Creating a new Loop
Section titled “Creating a new Loop”- Go to Console → Loops (under Connect)
- Choose Create Loop
- Pick the trigger type: Event-based or Scheduled
- Give the Loop a name under Loop name (e.g., “GitHub Issue Triage”)
- For an event Loop: under When this happens, pick the Connection and the Trigger event (e.g., GitHub → Issue Opened). For a scheduled Loop: set the schedule, then write What should the agent do? under Instructions
- Under Then run this agent, pick the agent
- Under Conversation, choose a new conversation per trigger, one continuous conversation, or one conversation per item (an issue, a pull request, a page). For messages from customers there is nothing to choose: each customer keeps one ongoing conversation
- Choose Create Loop. The Loop is on as soon as it is created; pause it with the switch on its row
Scheduled Loops need an Internal agent. For an event Loop, the agent type depends on the event: events from your team’s own services (GitHub, Slack, Jira, Notion and the like) need an Internal agent, and messages from customers on a Channel need a Customer-facing agent.
Members can create scheduled Loops. Event Loops need an owner or admin, unless your organization has member governance on, in which case a member’s event Loop waits for approval.
Event Loops vs. scheduled Loops
Section titled “Event Loops vs. scheduled Loops”| Event Loop | Scheduled Loop | |
|---|---|---|
| Trigger | An event in a connected service, or a message on a Channel | A schedule |
| Agent input | A summary of the incoming event | Your Instructions text |
| Template variables | Not supported — Auteryn formats the event for the agent | No event payload |
For event Loops, you do not write a separate “agent prompt” with {{event.title}} variables. Auteryn passes the message, or a summary of the event, to the agent directly.
Testing a Loop
Section titled “Testing a Loop”To start a scheduled Loop now, choose Run on its row (the Loop must be on). Event Loops have no Run button: test one by making its event happen (open a test issue, send a test message).
Loop run history
Section titled “Loop run history”Each triggered run appears in Runs. Open one to see what started it (Scheduled, Run now, or Event and its source) and:
- Timestamp, trigger source, status, credits used
- Full agent output and any errors