When should you use webhooks?
- You want to know about changes in the external API in real time
- You want to build a real-time data sync from the external API to your product
- You don’t want to deal with how each API implements webhooks, subscriptions, or attributing webhooks to users
- You don’t want to build and maintain infrastructure to handle webhook floods, debouncing, etc.
- Listen to “contact updated” webhooks from HubSpot, Attio, etc.
- Trigger an “order” sync run whenever Shopify sends a “new order” webhook
Key facts
- Incoming webhooks are processed by Nango’s infrastructure
- It auto-scales and provides tools to handle webhook floods, debouncing, etc.
- You have full control over webhook processing
- Each webhook gets attributed to its corresponding Connection (a user or organization that has set up a specific integration)
- Webhooks can be forwarded to your app or trigger a Function in Nango for processing
- Webhooks can be combined with syncs to create real-time syncs to your product
- All incoming webhooks create detailed logs in Nango’s logs
How webhooks work
- Configure webhooks for your integration (if necessary, Nango provides docs)
- Nango enables the webhooks you want for each account that connects (if required by the API)
- Nango processes incoming webhooks and attributes them to the correct account
- You decide for each webhook type how it gets processed:
- Forward to your backend
- Trigger a Function in Nango to process the webhook
- Nango stores detailed logs about each incoming webhook and its associated processing