Integrations

Integrations connect Breeze to the systems your team already depends on for service delivery. Instead of moving data manually between tools, you can route events and workflow state to communication platforms, PSA systems, and monitoring destinations from one control plane.

Integration Categories

Breeze organizes integrations into three practical categories:

• Communication: route alerts and operational messages to chat and incident channels.
• PSA / Ticketing: synchronize service workflows with the systems used for case and customer operations.
• Monitoring: forward selected telemetry into broader observability pipelines.

PSA-Centric Workflows

PSA integrations are the deepest operational path and are designed for managed-service execution. Connections are organization-scoped with encrypted credential handling, provider-specific configuration, and lifecycle management for tenant-specific setups.

For multi-customer environments, each organization can run different integrations and credentials without cross-tenant bleed.

Signed Webhooks

Outbound webhooks are HMAC-signed so downstream receivers can confirm a payload originated from Breeze and was not modified in transit. The signing key is configured per webhook, and the signature travels alongside the payload — receivers recompute and compare in constant time before accepting the event.

Legacy header-secret webhooks still deliver, but emit deprecation warnings so existing integrations can migrate on their own timeline. SSO token-exchange responses are following the same pattern: refresh tokens are moving to the standard OAuth location, with Deprecation and Sunset headers giving custom SSO integrations a clean migration window before the legacy shape is removed.

See the webhook docs for a full verification example and the migration checklist.

Operational Controls

Integration configuration changes are auditable, and endpoints are designed for controlled setup, validation, and update workflows. That matters when platform operations, service desk, and customer success all share ownership of the same connectors.

Why Teams Adopt It

Integrations reduce copy-paste between tools, shorten incident handoff time, and keep Breeze events aligned with the systems where teams actually triage, escalate, and close work.