Project integrations

Project integrations decide where one project sends notifications, creates follow-up work, links source repositories, and calls custom automation. Configure them per project so alerts and issue workflows match the team that owns the service.

What project integrations control

Integrations connect Errorgap evidence to the tools your team already uses. A project can connect messaging, issue tracking, source hosting, and webhooks independently.

• Slack sends project notifications to the channels responders watch.
• GitHub and GitLab connect errors to repository and issue workflows.
• Jira sends actionable work into planning and follow-up queues.
• Webhooks call custom endpoints owned by your team.

Open integrations

1. Open the project you want to configure.
2. Go to Project settings.
3. Select the Integrations tab.
4. Use the provider list to switch between messaging, issue tracking, and webhook settings.

Choose a provider

The integrations page groups providers by workflow. Pick the provider that owns the next step for this project rather than copying settings from unrelated services.

• Use one alert channel per ownership group when possible.
• Choose the repository where fixes for this project are reviewed.
• Choose the issue tracker project where production follow-up is prioritized.
• Use webhooks only for stable automation endpoints your team maintains.

Connect and test

After saving a provider, test it with a safe error group or non-production project before relying on it during an incident.

1. Confirm the provider shows as connected.
2. Create or link a test issue from a low-risk group when configuring issue tracking.
3. Trigger a safe notification when configuring messaging or webhooks.
4. Check the destination tool for useful titles, links, and context.

Maintain connections

Review integrations when project ownership changes, channels are renamed, repositories move, or issue workflows change.

• Remove or update stale destinations so alerts do not disappear into old channels.
• Keep repository settings aligned with the codebase shown in stack traces.
• Check project integrations after rotating provider credentials or changing access.

Privacy review

Integrations can send Errorgap context outside the product. Review redaction and project privacy settings before enabling a new destination, especially for webhooks and issue trackers that may be visible to broader audiences.