Integrations, labeled honestly.
Every entry below says exactly what it is: a shipped connector, an open standard the product implements, or something you build with the API. Nothing is a logo tile for a connector that doesn’t exist.
Identity
Sign-in via any SAML 2.0 identity provider, including Microsoft Entra ID and Okta.
Data flow: Receives signed assertions from your IdP at login. No standing directory access.
Sign-in via any OIDC provider, including Google Workspace.
Data flow: Exchanges an authorization code for identity claims at login.
Automatic provisioning and deprovisioning from Entra ID, Okta, or any SCIM 2.0 client.
Data flow: Your IdP pushes user create, update, and deactivate events to the SCIM endpoint.
Communication
Outbound alerts by webhook, threaded delivery with a bot token, and reply sync with a signing secret.
Data flow: Posts request updates to a channel; with reply sync enabled, thread replies flow back into the ticket.
Adaptive Card alerts by webhook, or threaded two-way delivery through Microsoft Graph.
Data flow: Posts request updates to a channel; with a Graph subscription, Teams replies sync back into the ticket.
Inbound email creates and threads requests; outbound mail carries replies and notifications.
Data flow: Reads mail sent to the workspace address; sends transactional and reply mail from it.
Migration
Pulls tickets, requesters, tags, and conversations directly from Zendesk.
Data flow: Read-only API access to your Zendesk instance during the import run.
Pulls tickets and conversations directly from Freshdesk.
Data flow: Read-only API access to your Freshdesk instance during the import run.
Pulls requests and comments directly from Jira Service Management.
Data flow: Read-only API access to your Jira instance during the import run.
Imports a Confluence space into the knowledge base, including JSM knowledge bases.
Data flow: Read-only API access to the Confluence space during the import run.
Imports tickets, users, and knowledge articles from CSV exports of any tool.
Data flow: Processes the file you upload; nothing leaves the workspace.
Security and observability
Audit events to Splunk, Datadog, Elastic, Sentinel, or Sumo via signed webhooks or a pull API.
Data flow: Pushes HMAC-signed audit events to your endpoint, or your SIEM polls the cursor-paginated stream.
A bearer-authenticated metrics endpoint for scraping operational health.
Data flow: Your collector scrapes aggregate counters; no request content is exposed.
Platform
Org-scoped API keys with granular scopes, rate limits, and audit logging.
Data flow: Whatever the key's scopes allow, recorded in the audit log per call.
HMAC-SHA256 signed event delivery with retries for request and audit events.
Data flow: Pushes the events you subscribe to at your endpoint.
Attachment storage on AWS S3 or any S3-compatible object store (self-hosted).
Data flow: Attachments are written to and served from your bucket.
Optional malware scanning of uploads against a ClamAV daemon.
Data flow: Attachment bytes are streamed to your ClamAV instance for a verdict.
Device management, CMDB sync, HRIS onboarding flows, and paging tools wire up through the REST API and signed webhooks. There is no packaged connector for these today, and this page won't pretend otherwise.
Data flow: You decide: the API is scoped per key and every call is audited.
Something missing?
The REST API is scoped per key and every call is audited, so wiring your own connection is a supported path, and the docs treat it as one.