Ticketing Integrations
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.
Notification Channels¶
Alerts can be delivered to team communication platforms when workflow conditions are met:
- Email - Direct notifications to specified addresses, asset owners, or project members
- Slack - Messages posted to channels via incoming webhooks
- Microsoft Teams - Messages posted to channels via Teams Workflows webhooks
- Discord - Channel webhook notifications; see Discord Setup
Ticketing Systems¶
Security issues can be exported to ticketing platforms for tracking and remediation:
- Jira - Tickets created with customizable field mappings for Cloud and Server instances
- Azure Boards - Work items created in Azure DevOps with PAT or Entra auth, field mappings, and bi-directional status sync
- Seemplicity - Findings routed into the Seemplicity Remediation Operations platform (managed by Seemplicity)
Configuration¶
Integrations are used through workflow actions:
- Navigate to Workflows → Create
- Configure a trigger and optional conditions
- Add a Notify or Export action
- Select the integration type and configure the required settings
- Save the workflow
Webhook Integration¶
Send JSON payloads to your own publicly reachable HTTP endpoint with the Webhook 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.