We’re introducing a new webhook event: data_export.sync_failed, designed to help you proactively monitor the health of your data exports in real-time.

🆕 What’s new?

We've added a new data_export.sync_failed webhook event, that triggers automatically whenever a scheduled or manual data export sync to your configured destination fails. 

Instead of waiting for a manual check in , your system will instantly receive an event payload containing context about the failed run, helping your team identify the issue immediately.

💡 Why it matters

• Proactive Monitoring: You no longer need to check the Stigg app manually or wait to discover stale data in your warehouse.
• Automated Alerting: Seamlessly pipe this webhook into your incident management tools (like PagerDuty or Opsgenie) or team communication channels (like a dedicated Slack channel) to alert your data or engineering team the second an issue occurs.
• Uninterrupted Data Reliability: Ensuring your Stigg data (Customer Data, Product Catalog, and Usage Tracking) successfully reaches your infrastructure is critical. This event closes the loop on data observability so you can keep your downstream reporting accurate and up to date.

⚒️ Get started

1. In the Stigg app, navigate to the Settings > Webhooks section.
2. Click + Add webhook (or edit an existing one).
3. Under the event triggers list, select the data_export.sync_failed event.

For complete details on the event payload and schema, check out the Webhook API Reference documentation.

📦 Availability

Available immediately to all customers that use the new data export pipeline.