# Configure a supported integration

Connect, configure, review, reconnect, or disconnect a supported workspace integration.

## Before you start

### Intended audience

Workspace managers who maintain provider connections.

### Required permissions

You need workspace-manager access. The provider can require separate administrator approval.


### Prerequisites

- Have workspace-manager access in Tellagen.
- For OAuth, have permission to approve the intended provider account or workspace.
- For credential providers, have the required API key and provider-specific account values.
- For a custom resolver, have the exact HTTPS endpoint, authentication values, request template, and response paths.

## Procedure

<a id="phase-select-a-provider"></a>

### Select a provider

<a id="step-open-integrations"></a>

1. **Open integrations.** Open Settings. Select Integrations.

<a id="phase-connect-slack"></a>

### Connect Slack

<a id="step-connect-slack"></a>

2. **Connect Slack.** Select Connect Slack. Approve consent for the intended Slack workspace. Return to Integrations. Confirm Connected, Workspace, and Bot on the Slack card.

![Slack integration card in the Not connected state with Connect Slack.](https://tellagen.com/help/assets/integrations-slack-card.webp)

This honest Slack example is not connected. Select Connect Slack to start its OAuth path.

<a id="step-configure-slack-workflows"></a>

3. **Configure Slack workflows.** In Alert channel monitoring, choose channels and select Save alert channels. In Incident channels, set Create a Slack channel for new incidents and the related channel options. Select Save channel settings. Use Conditional notifications for rule-based destinations. In Slack utilities, set AI bot responses or use Flush cache when required.

<a id="step-maintain-slack"></a>

4. **Maintain Slack.** Select Reconnect Slack when Slack authorization changes. Select Disconnect only when future Slack workflows must stop. Disconnect removes the Slack credentials and workspace mapping. Existing incident data and saved incident Slack context stay in Tellagen. Slack channel creation, channel name, responder invitations, and bot-query settings are preserved for a later connection.

<a id="phase-connect-google-meet"></a>

### Connect Google Meet

<a id="step-connect-google-meet"></a>

5. **Connect Google Meet.** Select Connect. Approve Google consent for the account that can create incident meetings. Return to Integrations and confirm Connected. This connection enables video calls from incident panels.

<a id="step-maintain-google-meet"></a>

6. **Maintain Google Meet.** When the card shows Needs re-auth and “Needs re-authorization. Please reconnect.”, select Reconnect and complete consent. Select Disconnect to clear the saved Google OAuth connection fields, including tokens, scopes, expiry, and connection metadata. Video calls from incident panels stop until you connect again.

<a id="phase-connect-intercom"></a>

### Connect Intercom

<a id="step-connect-intercom"></a>

7. **Connect Intercom.** Select Connect. Approve Intercom consent for the intended workspace. Return to Integrations and confirm Connected. Confirm the workspace ID when the card shows it.

<a id="step-set-intercom-preferences"></a>

8. **Set Intercom preferences.** Set Auto-sync interval, Customer ID attribute, and Show conversation messages. Select Save. These settings control conversation sync and how customer identity and messages appear on incidents.

<a id="step-maintain-intercom"></a>

9. **Maintain Intercom.** Select Reconnect when Intercom authorization changes. Select Disconnect to clear the Intercom connection fields. Disconnect keeps the saved display mode, Auto-sync interval, Customer ID attribute, and Show conversation messages preferences.

<a id="phase-connect-confluence"></a>

### Connect Confluence

<a id="step-connect-confluence"></a>

10. **Connect Confluence.** Select Connect. Approve Atlassian consent for the intended Confluence site. Return to Integrations and confirm Connected to followed by the correct site name.

<a id="step-maintain-confluence"></a>

11. **Maintain Confluence.** Select Reconnect when Confluence authorization changes. Select Disconnect only when exports must stop. Disconnect clears all Confluence integration settings, including the connection, site identity, and default space.

<a id="phase-configure-credential-providers"></a>

### Configure credential providers

<a id="step-configure-stripe"></a>

12. **Configure Stripe.** Turn on Enabled. Enter API key and Stripe customer metadata key. The metadata key accepts letters, numbers, dots, underscores, and hyphens. Select Save and confirm Configured. When the card shows Test, select it to validate the API key.

<a id="step-configure-recurly"></a>

13. **Configure Recurly.** Turn on Enabled. Enter API key and Subdomain for the intended Recurly account. Select Save and confirm Configured.

<a id="phase-configure-alerting-providers"></a>

### Configure alerting providers

<a id="step-configure-alerting-providers"></a>

14. **Configure alerting providers.** For PagerDuty, Opsgenie, and Rootly, configure each provider that the workspace uses. Turn on Enabled. Enter the API key. Select Save. Confirm Configured on the provider card.

<a id="phase-configure-customer-resolution"></a>

### Configure customer resolution

<a id="step-configure-customer-resolver"></a>

15. **Configure Customer resolver.** Open Customer resolver and turn on Enabled. Enter Resolver URL, Auth type, Auth value, and Header name for API key header or Custom header. Enter Request body template with {{external_id}}, Response email path, and Response name path. Select Save.

<a id="step-test-customer-resolver"></a>

16. **Test Customer resolver.** In Test resolver, enter Test external customer ID and select Test. A successful result shows Resolved with the customer email and name.

<a id="phase-verify-and-recover"></a>

### Verify and recover

<a id="step-refresh-missing-evidence"></a>

17. **Refresh missing evidence.** If current evidence is missing after a connection or save, reload Integrations. Use Retry in the affected Slack section. Use Test for Stripe or Customer resolver. Check the provider account, scopes, and workspace permission before you replace credentials.

## You are done when…

Each configured provider has source-specific proof: Slack shows Connected with Workspace and Bot, Google Meet shows Connected, Intercom shows Connected with its workspace ID when available, Confluence shows Connected to the site, credential providers show Configured, and Customer resolver returns a successful Test result.

## Troubleshooting

<a id="troubleshooting-oauth-returns-to-not-connected-or-needs-re-auth"></a>

### OAuth returns to Not connected or Needs re-auth.

Select Connect or Reconnect for the intended account. Complete consent. If the status does not become Connected, ask the provider administrator to review the authorization restriction.

<a id="troubleshooting-slack-does-not-show-workspace-and-bot"></a>

### Slack does not show Workspace and Bot.

Select Reconnect Slack and approve the intended workspace. Confirm Connected, Workspace, and Bot before you depend on Slack workflows.

<a id="troubleshooting-google-meet-shows-needs-re-auth"></a>

### Google Meet shows Needs re-auth.

Select Reconnect. Complete Google consent. Confirm Connected before you create a meeting from an incident panel.

<a id="troubleshooting-intercom-preferences-do-not-update"></a>

### Intercom preferences do not update.

Confirm the card is Connected. Set Auto-sync interval, Customer ID attribute, or Show conversation messages. Select Save in the Intercom card.

<a id="troubleshooting-confluence-does-not-show-the-intended-site"></a>

### Confluence does not show the intended site.

Select Reconnect and approve the intended Atlassian site. Confirm Connected to and the correct site name before you export a postmortem.

<a id="troubleshooting-stripe-does-not-show-configured-or-test-fails"></a>

### Stripe does not show Configured or Test fails.

Confirm Enabled, API key, and Stripe customer metadata key. Select Save. Then select Test when the action is available.

<a id="troubleshooting-recurly-does-not-show-configured"></a>

### Recurly does not show Configured.

Confirm Enabled, API key, and Subdomain for the intended account. Select Save.

<a id="troubleshooting-the-custom-resolver-test-fails"></a>

### The custom resolver test fails.

Check Resolver URL, Auth type, Auth value, Header name, Request body template, Response email path, and Response name path. Select Save. Run Test again with a known external customer ID.

<a id="troubleshooting-connected-provider-data-is-missing"></a>

### Connected provider data is missing.

Reload the page after a refresh failure. Use the local Retry or Test action when the section provides one. Then review the provider scope and workspace permissions.

## Related articles

- **Recommended next task:** [Declare an incident from Slack](https://tellagen.com/help/declare-incident-from-slack)
- [Assess customer impact](https://tellagen.com/help/assess-customer-impact)


## Continue through the incident lifecycle

- **Previous task:** [Configure MCP tools for Diagnosis](https://tellagen.com/help/configure-mcp-tools-for-diagnosis)
- **Next task:** [Check workspace incident readiness](https://tellagen.com/help/check-incident-readiness)
- [Back to Support Center](https://tellagen.com/help#help-search)

## Last verified date

2026-08-29