Triggers & Events
Use when: An external system should call Auteryn when something happens.
When you create a webhook trigger, Auteryn gives you a unique URL:
https://hooks.auteryn.ai/v1/flows/{flow-id}/webhookConfigure your external service to POST to this URL on the relevant event.
Security: Every webhook URL has a secret for request verification. Set the secret in the external service — Auteryn rejects requests with invalid signatures.
Trigger directly from GitHub events without manual webhook setup:
issue.opened— new issue createdissue.labeled— issue labeledpull_request.opened— new PR openedpull_request.review_requested— review requestedworkflow_run.completed— CI run finished
Setup:
- Select trigger type GitHub Event
- Choose the event type and repository
- Save and enable
Fire a flow when a message is sent in a Slack channel:
- Select trigger type Slack Message
- Choose the channel to monitor
- Optionally filter by keyword
Only fires when the message contains the specified keyword.
Trigger a flow when an email arrives in a connected Gmail inbox:
- Select trigger type Email
- Choose the Gmail account
- Set filters: sender email, subject contains, label
Run your agent on a timetable. See Scheduling →.
A Manual trigger flow only runs when you click Run Now from the Console or call the trigger API endpoint.
Useful for on-demand reports, testing, or workflows that need a human approval step before execution.
Payload format
All webhook and event triggers receive a JSON payload. The full payload is accessible via {{event.raw}}.
Example — GitHub issue opened:
{ "action": "opened", "issue": { "number": 42, "title": "Login button not responding on mobile", "body": "Steps to reproduce...", "html_url": "https://github.com/acme/app/issues/42", "user": { "login": "alice" } }, "repository": { "name": "app", "full_name": "acme/app" }}