Notification and ticketing integrations enable security findings to be routed to the appropriate teams through existing communication channels and issue tracking systems. All integrations are configured as actions within [Workflows](<https://docs.escape.tech/documentation/automate/workflows/index.md>).

## Notification Channels

Alerts can be delivered to team communication platforms when workflow conditions are met:

- **[Email](<https://docs.escape.tech/documentation/automate/notifications-ticketing/email/index.md>)** - Direct notifications to specified addresses, asset owners, or project members
- **[Slack](<https://docs.escape.tech/documentation/automate/notifications-ticketing/slack/index.md>)** - Messages posted to channels via incoming webhooks
- **[Microsoft Teams](<https://docs.escape.tech/documentation/automate/notifications-ticketing/teams/index.md>)** - Messages posted to channels via Teams Workflows webhooks
- **Discord** - Channel webhook notifications; see [Discord Setup](<https://docs.escape.tech/documentation/automate/workflows/actions/#discord-setup>)

## Ticketing Systems

Security issues can be exported to ticketing platforms for tracking and remediation:

- **[Jira](<https://docs.escape.tech/documentation/automate/notifications-ticketing/jira/index.md>)** - Tickets created with customizable field mappings for Cloud and Server instances
- **[Azure Boards](<https://docs.escape.tech/documentation/automate/notifications-ticketing/azure-boards/index.md>)** - Work items created in Azure DevOps with PAT or Entra auth, field mappings, and bi-directional status sync
- **[Seemplicity](<https://docs.escape.tech/documentation/automate/notifications-ticketing/seemplicity/index.md>)** - Findings routed into the Seemplicity Remediation Operations platform (managed by Seemplicity)

## Configuration

Integrations are used through workflow actions:

1. Navigate to **Workflows** → **Create**
2. Configure a [trigger](<https://docs.escape.tech/documentation/automate/workflows/triggers/index.md>) and optional [conditions](<https://docs.escape.tech/documentation/automate/workflows/conditions/index.md>)
3. Add a **Notify** or **Export** action
4. Select the integration type and configure the required settings
5. Save the workflow

## Webhook Integration

Send JSON payloads to your own publicly reachable HTTP endpoint with the [Webhook](<https://docs.escape.tech/documentation/automate/workflows/webhook/index.md>) action. Set the URL directly in the workflow action; no separate integration configuration is required. Webhook exports originate from platform infrastructure and don’t route through a Private Location.

## Severity Routing

Workflow conditions can be configured to route findings based on severity, category, or other attributes. This allows critical vulnerabilities to be escalated through different channels than informational findings.