Skip to main content

Documentation Index

Fetch the complete documentation index at: https://nango.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Many APIs can notify you when something changes, but each provider has its own webhook registration flow, payload shape, retries, and connection mapping. Nango gives external APIs one integration-specific webhook URL and attributes incoming events to the right connection. You can forward those webhooks to your app, process them in Nango functions, or combine them with sync functions for reliable near real-time data.

​
When this fits

Use Nango for external webhooks when:
  • A provider can notify you about changes faster than polling alone.
  • You need to map incoming provider webhooks to Nango connections.
  • Webhooks should trigger follow-up API requests with the user’s credentials.
  • You want webhook events and related API calls visible in Nango logs.
  • You need real-time sync behavior without relying only on provider webhooks.
For outgoing webhooks from Nango to your app, see Receive webhooks from Nango.

​
How Nango fits in

  1. You register the Nango webhook URL in the provider’s developer portal.
  2. The provider sends events to Nango.
  3. Nango attributes each event to the right integration and connection when possible.
  4. Nango forwards the event to your app or routes it into a function.
  5. If the event updates synced data, the function writes records to Nango’s cache.

​
Common patterns

  • Forward the provider webhook payload to your app for custom handling.
  • Use a webhook function to fetch the changed object and update the records cache.
  • Keep a periodic sync function as reconciliation in case provider webhooks are missed.
  • Register per-connection provider webhooks in an event function after authorization.