Integrations

Overview

Integrations live under Settings → Integrations. Each one has its own configuration page, status indicator, and event log so you can see what came in or went out, with timestamps. Credentials are encrypted at rest and never appear in logs.

The supported integrations today fall into two groups: built-in connectors for inbound email and chat-based notifications, and generic webhooks for everything else.

Inbound email (SendGrid)

Email is Zentra’s primary intake channel. Inbound mail is parsed via SendGrid’s Inbound Parse webhook, which posts to /api/webhooks/inbound-email.

1. Add an MX record on a subdomain (e.g. support.yourcompany.com) that points at SendGrid.
2. In SendGrid, configure Inbound Parse to forward incoming mail to your Zentra deployment’s webhook URL.
3. Set the matching webhook secret under Settings → Integrations → Inbound email.

Replies to existing tickets thread automatically when the message references a known ticket id.

Slack notifications

Zentra delivers notifications to Slack via incoming webhook URLs. Configure under Settings → Integrations → Slack.

What you get today:

• One-way channel notifications for ticket events, SLA breach risk, change approvals.
• Workflow actions that post to a channel as part of an automation.

Two-way conversation (creating tickets from Slack, replying via Slack) is on the roadmap. For now, Slack is a notification surface; intake stays on email and the portal.

Microsoft Teams notifications

Same surface as Slack via a configured Teams incoming webhook. Configure under Settings → Integrations → Microsoft Teams. Notification delivery on ticket events, SLA risk, and approval requests.

Google sign-in

Beyond the default email-and-password authentication, you can enable Google sign-in for users with a Google account. Configure under Settings → Authentication:

1. Create an OAuth 2.0 client in Google Cloud Console.
2. Add your Zentra deployment’s callback URL as an authorized redirect.
3. Paste the client ID and secret into Zentra and toggle Google sign-in on.

SAML, OIDC, and SCIM provisioning are not currently supported. Talk to us if those are evaluation requirements — they’re tracked.

AI (OpenAI)

Zentra’s AI features run on top of any OpenAI-compatible API. Add an OpenAI API key in Settings → Integrations → AI to enable:

• Ticket classification — assigns a category to every new ticket.
• Auto-resolution — attempts to resolve common requests using your knowledge base.

The model is configurable (default gpt-4o-mini). Without a key, both jobs are silently skipped.

Outbound webhooks

For anything not covered by a built-in connector, Zentra fires outbound webhooks to URLs you register. Configure under Settings → Integrations → Outbound webhooks.

Each subscription has:

• Target URL — where the payload is POSTed.
• Event filter — one or more events you want delivered (e.g. ticket.created, change.approved).
• Signing secret — Zentra signs every payload with HMAC-SHA256 over the body.
• Retry policy — bounded retries with exponential backoff. Failed deliveries are visible in the event log.

See the Webhooks & API reference for payload shape and signing details.

Generic inbound webhooks

Zentra accepts inbound POSTs on configurable paths under /api/webhooks/<name>. Use these to feed events from monitoring tools, deploy systems, or HR systems into the workflow engine.

Every inbound webhook endpoint can be:

• Secret-protected — request must include the configured shared secret header.
• Workflow-routed — the payload becomes the trigger event for a workflow definition.

On the roadmap

Native two-way connectors for the following are tracked but not yet shipped. In the meantime, all of these can be wired via outbound webhooks plus a small adapter on your side:

• PagerDuty, Datadog, Grafana (alerts → tickets, status sync)
• GitHub (issue sync, deploy events → change records)
• Okta, Microsoft Entra ID (SSO + SCIM provisioning)
• Jamf, Intune (asset auto-discovery)
• AWS, Azure, GCP (CMDB population from cloud accounts)

If one of these is a hard evaluation requirement for you, tell us — your team’s ask helps prioritize the order we build them.

Next

• Webhooks & API — payload shapes, signing, idempotency
• Automation — call any of these from a workflow action
• Talk to us — about a connector you need