Triggers & Events
Flows use one of two trigger types: event or schedule. GitHub, Slack, email, and webhooks are all event flows tied to a connection and trigger event — not separate trigger type pickers.
Use when: An external system should call Auteryn when something happens.
Verified integrations (GitHub, Slack, etc.) receive URLs like:
https://webhooks.auteryn.ai/webhook/in/v/{slug}/{connection_id}Custom webhook connections use:
https://api.auteryn.ai/webhook/in/c/{token}(Host may vary if your org sets WEBHOOK_BASE_URL.)
Configure your external service to POST to this URL on the relevant event.
Create an event flow with a GitHub connection. Available trigger events include:
issues.openedissues.closedpull_request.openedpull_request.mergedpush
Setup:
- Connect GitHub under Integrations
- Create a new Event flow
- Select the GitHub connection and trigger event
- Bind an Internal agent
Create an event flow with a Slack connection:
- Connect Slack under Integrations
- Create an Event flow → Slack → message event
- Bind an Internal agent
Requires an Internal agent (Slack workspace events are internal-category).
Connect the Email channel under Integrations. It gives you an Auteryn address.
- Forward your support inbox to that address
- Attach the channel to a Customer-facing agent
- Each email that arrives runs the agent, and it replies by email
Run your agent on a timetable. See Scheduling →. Requires an Internal agent.
Click Run Now on any enabled flow in the Console to trigger it on demand.
Payload format
Section titled “Payload format”Event flows pass the incoming webhook or platform payload to the agent as context. You do not configure template variables like {{event.raw}} in the flow editor — the worker formats the payload automatically.
Example — GitHub issue opened (simplified):
{ "action": "opened", "issue": { "number": 42, "title": "Login button not responding on mobile", "body": "Steps to reproduce..." }, "repository": { "full_name": "acme/app" }}
