Current support systems
Slack, GitHub, Gmail, Zendesk, Intercom, and GranolaConnect the systems that already own the work.
Bring support, engineering, email, commerce, analytics, messaging, meeting, and public app-review evidence into BTX with explicit availability for every connection.
BTX connects with Slack, GitHub, Gmail, Zendesk, Intercom, Granola, Shopify, and the Apple and Google app stores. Mixpanel and Twilio are project-specific, while Linear is planned. The catalog below shows what each connection does and whether it is currently available.
Commerce and reviews
Shopify, Apple App Store, and Google PlayScoped or planned
Mixpanel and Twilio project-specific; Linear plannedKeep ownership explicit.
A connected system should continue to own the records and actions it is responsible for. BTX adds customer and product context, preserves source links, and exposes only the bounded workflow that the team has configured.
That matters when a Zendesk email thread remains externally owned, a Gmail inbox controls the sender, or a GitHub repository controls issue permissions and assignees.
Use integrations inside the operator workflow.
Slack
Bind project channels, ask customer questions, receive conversation notifications, inspect citations, and review GitHub actions.
GitHub
Select a repository, prepare a customer-evidence issue, choose an assignee, preserve the source, and close linked work.
Gmail
Connect shared inboxes, synchronize messages, send or reply from an authorized sender, and preserve attachments.
Zendesk
Synchronize tickets and comments while keeping Zendesk-owned email threads external and source-linked.
Intercom
Connect a project, synchronize conversations, contacts, admins, and message parts, and inspect sync health.
Granola
Bring selected meeting notes and transcripts into the recording and relationship review workflow.
Shopify
Connect stores for customer and order context, published knowledge delivery, storefront messaging, and bounded return workflows.
App stores
Read public Apple App Store and Google Play reviews for configured customer applications.
Describe project-specific connections honestly.
Mixpanel
Load allowlisted customer-profile and product-usage context for explicitly configured projects.
Twilio
Receive, synchronize, and reply to SMS through a project-owned sender with provider status and opt-out handling.
Linear
Planned as a separate product and engineering work connection; no shipped integration is claimed yet.
Availability
Project-specific and planned rows stay labeled until setup, permissions, and support expectations are generalized.
Current integration catalog
| System | What BTX uses | Availability |
|---|---|---|
| Slack | Project channels, thread context, attachments, notifications, and reviewed agent actions | Current |
| GitHub | Repository selection, issue creation, assignee selection, source links, and close actions | Current |
| Gmail | Shared inbox synchronization, sender selection, messages, replies, and attachments | Current |
| Zendesk | Tickets, comments, external ownership, and source navigation | Current |
| Intercom | Connections, contacts, admins, conversations, message parts, scheduled sync, and sync health | Controlled rollout |
| Granola | Meeting notes, transcripts, synchronization, and source links | Current |
| Shopify | Customer and order context, published knowledge, storefront messaging, multiple stores, and bounded return workflows | Controlled rollout |
| Apple App Store | Public reviews, ratings, app versions, listing links, and rating trends | Current |
| Google Play | Public reviews, ratings, app versions, listing links, and rating trends | Current |
| Mixpanel | Allowlisted customer-profile and product-usage context | Project-specific |
| Twilio | Inbound and outbound SMS, history synchronization, delivery status, and opt-out handling | Project-specific |
| Linear | Planned product and engineering work connection | Planned |
Availability describes the current product contract. Controlled-rollout and project-specific connections may require guided setup. Planned is not a shipped capability.
Frequently asked
Does BTX replace the connected system?
No. BTX preserves explicit ownership. For example, Zendesk can remain the ticket owner, Gmail controls the sending inbox, GitHub controls repository permissions, and app stores remain the public review source.
Are all integrations and setup flows generally available?
No. Intercom and Shopify are in controlled rollout. Mixpanel and Twilio are project-specific. Linear is planned. The catalog labels each status rather than presenting every row as self-serve.
How are integration permissions handled?
Each connection uses the authorization and project scope required by that provider. Actions remain constrained by both the connected system and the BTX project.