Integrations
Integrations overview
API, inbound webhook, Stripe, or Zapier — which to use.
Audryo’s canonical ingest path is the HTTP API with a workspace token. Integrations exist for sources that cannot do that, or for pushing events out.
Choose a path
| Source | Use |
|---|---|
| Your app / backend | Contacts API and Events API |
| HMAC-only vendor, custom JSON shape | Inbound webhook |
| Stripe billing | Stripe |
| Zapier / Make-style automation | Zapier |
| Your own HTTPS receiver | Outbound webhooks |
| Resend / Mailgun delivery events | Provider webhook on Connect your ESP. Custom SMTP has no delivery events |
All inbound paths hit the same ingestion and Journey evaluation. The difference is authentication and payload mapping, not a second runtime.
What not to build
- Browser automation against the Audryo UI
- Polling every minute instead of sending events when they happen
- A second “consent” boolean in Stripe metadata instead of the consent ledger