Activity logs
Every action that happens in Nango produces an operation in the Logs tab of your dashboard. Operations are organized into two levels:- Operations: High-level actions such as sync executed, connection created, or webhook processed.
- Log messages: Nested within operations, these capture granular detail — HTTP requests, data validation warnings, custom log messages from your code, and errors returned by external APIs.
You can write your own log messages from inside your integration functions using the built-in
nango.log() helper. These appear alongside Nango’s own log messages in the same operation view.Filtering and searching
The Logs tab lets you filter and search across all operations by:- Integration (e.g., Salesforce, GitHub)
- Connection ID
- Operation type (sync, action, webhook, auth)
- Status (success, failure, running)
- Time range
Useful signals to watch
| Signal | What to look for |
|---|---|
| Sync health | Operations with failed status on recurring syncs |
| Action errors | 4xx / 5xx responses from external API calls |
| Connection status | Auth failures or token refresh errors |
| Webhook delivery | Incoming external webhooks that errored during processing |
Webhook notifications to your backend
Nango can notify your backend in real time when integration activity occurs. Configure a webhook URL in your environment settings and Nango will send HTTP POST requests for the following events:| Event | When it fires |
|---|---|
| Sync completed | After each sync execution (success or failure) |
| New records available | When a sync produces new or updated records |
| Auth created | When a new connection is established |
| Auth failed | When a connection’s credentials become invalid |
| External webhook received | When Nango receives a webhook from a third-party API |
Setting up webhook notifications
Open environment settings
In the Nango dashboard, go to Environment Settings for the environment you want to configure (dev or prod).
Enter your webhook URL
Under Webhook URL, enter the HTTPS endpoint on your server that should receive Nango notifications. Nango sends a POST request with a JSON body to this URL.
Webhook payload structure
Nango signs webhook payloads so you can verify they originated from Nango. TheX-Nango-Signature header contains an HMAC-SHA256 signature computed using your secret key.
Each payload includes the event type, environment, connection ID, and integration name — enough context to route and process the event without an additional API call.
OpenTelemetry export
For advanced monitoring and alerting, Nango exports operation data as OpenTelemetry traces to any compatible collector (Datadog, Grafana, Honeycomb, etc.). The following operation types are exported:- Sync executions
- Action executions
- Third-party API webhook executions
- Proxied requests
- Build custom dashboards across integrations
- Set up alerting segmented by customer or integration
- Correlate Nango operations with your own application traces
Setting up OTel export
Open environment settings
In the Nango dashboard, navigate to Environment Settings for your environment.
Configure the OTel endpoint
Under OpenTelemetry Export, enter:
- Endpoint URL: The URL of your OpenTelemetry collector (e.g.,
https://my.otlp.collector:4318) - Headers (optional): Authorization headers required by your collector