Integrations Overview

RectifAI organizes integrations by function rather than only by vendor.

This lets your team choose the provider that best fits each part of the incident lifecycle.

Integration categories

JSM

Used for:

• incident records
• project and issue type configuration
• status mapping
• problem records
• action items

Chat

Used for:

• incident channels
• notifications
• responder coordination

Supported providers:

• Slack
• Google Chat
• Microsoft Teams

Paging

Used for:

• alerting on-call responders
• acknowledging or resolving paging-side incidents where supported

Supported providers:

• PagerDuty
• JSM Operations

Engage

Used for:

• meeting and bridge workflows
• collaboration during active incidents

Supported providers:

• Zoom
• Google Meet
• Microsoft Teams

Connected vs default provider

There are two important states:

• Connected: the provider is authenticated and available
• Default: the provider is the one RectifAI will use for that function

You can connect more than one provider in a category, but only one should usually be the operational default.

Auth health

The Integrations area also shows whether a provider is:

• not connected
• connected
• connected but currently failing auth verification

If a provider shows an auth error, re-test the connection or reconnect it before relying on it during an incident.