Integrations
Every system Intertrace connects to, by purpose: what each sends or reads, how to test it, and what it doesn't do yet.
Where each connection lives
Connect → Integrations is where Intertrace reaches your people and tools: alerts and approval requests, your security tools and tickets. Each integration has one place it is set up. Sources Intertrace reads from (clouds, identity, code, SaaS AI) are set up in Discovery; model provider keys in Integrations → Model providers; MCP servers in the MCP hub. The Integrations Overview lists all of them with their state.
A connection reads Working only when its last delivery or test succeeded, Failing since … with the error when the last one failed, and Set up, not tested yet when it is saved and nothing was sent. Every sender records its outcome; Send test records like any other delivery.
Alerts and approvals
| Integration | Direction | What it carries | Test | Not supported yet |
|---|---|---|---|---|
| Slack (incoming webhook) | Sends | Critical and high findings; every approval request with buttons that open it in Intertrace | Send test | Approving from Slack |
| Microsoft Teams | Sends | Critical and high findings; approval requests as an Adaptive Card with one link to the inbox | Send test | Approving from Teams (by design: decisions happen in Intertrace) |
| PagerDuty | Sends | An incident per critical finding (high too, if switched on) | Send test | Acknowledge or resolve syncing back |
| Sends | Approval requests to approvers; each person chooses under Settings → Notifications | — | — | |
| Mattermost, approval webhook | Sends | Approval notices, set up with itr | — | Set up from the dashboard |
Security tools
| Integration | Direction | What it carries | Test | Not supported yet |
|---|---|---|---|---|
| Signed webhook | Sends | Every SIEM event (findings, decisions, incidents, HIRO) as signed JSON envelopes with retries; critical and high finding alerts | Send test | — |
| Datadog Logs | Sends | Each critical and high finding as a log (source intertrace) with a link back | Send test | Approvals and other events |
| Splunk HEC | Sends | Through the signed webhook and a forwarder | — | A direct Splunk destination from the dashboard |
| Microsoft Sentinel, CrowdStrike Falcon | — | Through the signed webhook | — | Native connectors |
Tickets
| Integration | Direction | What it carries | Test | Not supported yet |
|---|---|---|---|---|
| Jira Cloud | Both | An issue for a work item made from a finding; verified and closed through the API | Check connection (reads only) | Status sync back from Jira set up in the dashboard |
| GitHub Issues | Both | An issue in a saved repository for a work item | Check connection (reads only) | Status sync back set up in the dashboard |
| ServiceNow | Both | An incident per work item (reused by correlation id), resolved with a close code and notes; resolved incidents update the work item through a Business Rule | Check connection (reads only) | Tickets opened from incidents |
Open a ticket from a finding: Create work item → Also open a ticket in. Only trackers that are set up are offered.
Model providers
One editor for the organization's provider keys: saved or not, who saved it, 7-day use, and the last test with the reason and next step. Each provider gets only its own key. Providers the hosted gateway reaches only through Intertrace's own accounts (Azure OpenAI, AWS Bedrock, Vertex AI) are listed separately and take no organization key.