Webhooks
Send Errorgap events to custom automation endpoints while keeping payloads scoped and privacy-aware.
Webhooks connect Errorgap to custom workflows such as internal alerting, ticket enrichment, status automation, or data warehouses. Use them when a first-party integration does not fit the workflow.
What webhooks are for
- Notify an internal service when an error group changes state.
- Enrich incidents with data from another system.
- Forward selected production signals to a team-owned automation endpoint.
Connect a webhook
- Open project settings and select Integrations.
- Select Webhook.
- Enter the destination URL and any required settings exposed by your organization.
- Save and trigger a safe test event.
Choose destinations
Send webhooks to stable, team-owned endpoints. Avoid personal tunnels or temporary tools for production projects unless you are testing in a non-production environment.
Privacy and reliability
- Review redaction rules before sending payloads outside Errorgap.
- Use HTTPS destinations controlled by your organization.
- Design receivers to handle duplicate deliveries and temporary failures.
Troubleshooting
- Confirm the URL is reachable from Errorgap.
- Check receiver logs for rejected payloads or authentication failures.
- Use a safe test event before relying on a webhook for incident response.