Integrations

Connect external services so Supp can automatically create issues, post messages, send emails, and trigger webhooks when tickets are classified.

Supported Services

Issue Tracking

ProviderConnectionAction
GitHubOAuth or tokenCreate issues with labels and priority tags
LinearOAuth or API keyCreate issues with priority, team, and project
JiraOAuth or basic authCreate issues with project and type
NotionOAuthCreate pages in databases

Communication

ProviderConnectionAction
SlackOAuth or webhookPost to channels with rich Block Kit formatting
DiscordWebhookPost to channels
Microsoft TeamsWebhookPost to channels
Email (Resend)API keySend templated emails

CRM & Support

ProviderConnectionAction
ZendeskAPI keyCreate support tickets
IntercomOAuth or API keyCreate conversations
HubSpotAPI keyCreate tickets in pipelines
ShopifyAPI keyTag orders, update customers

Automation

ProviderConnectionAction
ZapierWebhook URLTrigger any Zap workflow
CustomHTTPS URLPOST JSON to any endpoint

Priority Mapping

When creating issues, Supp maps priority levels automatically:

Supp PriorityGitHub LabelLinearJira
criticalP0UrgentHighest
highP1HighHigh
mediumP2MediumMedium
lowP3LowLow

MCP Tools

ToolDescription
supp_integrationsList connected and available services
supp_connectGet OAuth URL or setup instructions
supp_disconnectDisconnect a service

Connecting via MCP

text
You: "What integrations are available?"
> supp_integrations()

You: "Connect GitHub"
> supp_connect(service: "github")
  Returns: OAuth URL — open to authorize

You: "Connect Slack"
> supp_connect(service: "slack")
  Returns: OAuth URL

You: "Disconnect Linear"
> supp_disconnect(service: "linear")

Multiple Connections

You can connect multiple instances of the same provider:

  • Two Slack workspaces (engineering + support)
  • Multiple GitHub repos
  • Different email addresses for different intents

Specify which integration to use in each routing rule's config.

Token Management

Supp automatically detects expired tokens and prompts you to reconnect. If a token fails 3 consecutive verification checks, the integration is auto-disconnected.