Event sources
Connect Sentry, Stripe, GitHub, Slack, or any Standard Webhooks publisher so their events trigger your AGNT5 workflows.
An event source is a third-party service that emits events AGNT5 turns into workflow triggers. Each one delivers events over a signed webhook: you store the provider’s signing secret once, then declare a trigger on any workflow that should run when an event arrives.
If you control the sending side, point any Standard Webhooks publisher straight at AGNT5 — see Webhooks. The pages here cover the providers that sign their deliveries their own way.
Supported sources
| Source | Emits | Signing secret |
|---|---|---|
| Standard Webhooks | Anything you publish | AGNT5-generated — copy in |
| Slack | Events API callbacks | Provider-issued — paste |
| GitHub | Repository and workflow events | AGNT5-generated — copy in |
| Stripe | Payment and billing events | Provider-issued — paste |
| Sentry | Issue and error alerts | Provider-issued — paste |
The shape of every setup
Connecting any event source follows the same four steps:
- Create the integration in Studio → Integrations and choose the target environment.
- Store the signing secret — generate one in AGNT5 (GitHub, Standard Webhooks) or paste the one the provider issues (Sentry, Stripe, Slack).
- Copy the webhook URL (
…/v1/webhooks/{source}/{integration_id}) into the provider’s webhook settings. - Declare a trigger on your workflow with
webhook("{source}", event="…").
The per-provider pages cover only what differs at steps 2 and 3 — where to find the secret, where to paste the URL, and which events the source emits. Steps 1 and 4, along with signature verification and delivery semantics, are identical everywhere and live in Webhooks.
Related
- Webhooks — the trigger mechanism, end to end
- Integrations — how credentials are stored and scoped