GET /v1/integrations returns the triggerable integration-event catalog for your brand. It lists every event you can build automations from — even for providers you haven’t connected yet — so an agent can see what’s possible before wiring anything. Requires the automations scope.
For each provider you get connected (an active connection exists) and, per event, provisioned (a Brew trigger already exists for it), plus the fieldKeys / requiredFieldKeys that event carries.
List the catalog
?provider= (clerk | stripe | stytch | supabase | workos | shopify | revenuecat). An unknown provider is a 400 INVALID_REQUEST.
From discovery to a live automation
- Pick an
eventTypefrom the catalog (e.g.user.created). - Connect the provider in the dashboard if
connectedisfalse— connecting provisions a Brew trigger for every supported event automatically. - Build + publish an automation wired to that trigger. A trigger only fires when at least one automation referencing it is
published. - Fire it (or let the provider’s webhook fire it). The trigger-fire API:
See also
GET /v1/integrationsin the Public API v1 reference (sidebar) — full schema.- Trigger automations from events — the dashboard connection flow.
- Errors —
NO_PUBLISHED_AUTOMATION,TRIGGER_EVENT_NOT_FOUND.
Need Help?
Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:- Self-Service Tools
- Talk to Our Team
Search Documentation
Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.
ChatGPT/Claude Integration
Click “Open in ChatGPT” at the top right of any page to analyze documentation with ChatGPT or Claude for deeper insights.