Integrations - Beamdesk Docs

Supported integrations

Beamdesk currently lists 23 implemented integrations on the integrations page: Shopify, WooCommerce, PrestaShop, Stripe, Slack, Microsoft Teams, Telegram, WhatsApp, WhatsApp Cloud, Twilio, Vapi, Sonetel, Instagram, Facebook Messenger, Twitter, Gmail, IMAP, GitHub, Linear, Sentry, Notion, Google Tag Manager (GTM), Fakturownia.

The setup pattern is consistent: connect the account, choose the workspace or queue, map fields, test with a live event, then decide which personas and automations may use the integration.

Common setup paths

Shopify

Connect the store, grant read access to customers and orders, map order status fields, then let support personas answer order lookup questions.

Stripe

Connect payments, choose invoice and subscription scopes, mask sensitive fields, then expose lookup tools to billing personas.

Slack

Authorize the workspace, pick escalation channels, configure thread format, and test human handoff notifications.

Microsoft Teams

Authorize the tenant, pick destination channels, configure escalation formatting, and verify delivery.

Gmail

Authorize the mailbox or alias, choose inbound labels, send a test email, and verify outbound reply identity.

IMAP

Connect any mailbox with standard IMAP access, map folders to queues, and confirm reply threading.

Connect the messaging provider, verify templates, map phone identities, and route conversations to the shared inbox.

GitHub

Connect repositories, subscribe to relevant events, and expose engineering context to triage personas.

API key management

Create and rotate keys in /settings/developer/api-keys. Use separate keys for production, staging, scripts, and partner systems. Assign scopes narrowly so a reporting job cannot write tickets and a widget cannot export audit logs.

X-API-Key: bd_live_********************************
Scopes:
  read:tickets
  write:tickets
  read:knowledge
  write:knowledge
  export:audit_log

Webhook configuration

Configure webhook destinations in /settings/developer/webhooks. Select events, add a destination URL, save the signing secret, and send a test event before enabling production delivery.

{
  "url": "https://example.com/webhooks/beamdesk",
  "events": ["ticket.created", "ticket.resolved", "audit.event"],
  "enabled": true
}

MCP server endpoint

Beamdesk exposes an MCP-compatible server at /api/mcp. It supports 22 tools, authenticates with the X-API-Key header, and uses JSON-RPC 2.0 with SSE for streamed tool responses.

curl -N https://app.beamdesk.com/api/mcp \
  -H "X-API-Key: $BEAMDESK_API_KEY" \
  -H "Accept: text/event-stream" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":"1","method":"tools/list"}'

Build with the API

Do not see yours? Connect via webhooks, custom tools API, or no-code automation-style integrations through our HTTP webhook surface. Most custom integrations need three pieces: an API key with narrow scopes, a webhook destination for Beamdesk events, and a custom HTTP tool if personas should fetch data during replies.

Open API reference