Integrations overview

What integrations do for you

Ochre's integrations bring outside data into the inbox where your team is already working. The agent reading a customer email about a billing issue shouldn't have to alt-tab to Stripe to see the plan and last invoice. They shouldn't open Linear in a new tab to file a bug. They shouldn't ping the engineer manually to ask if the bug fix shipped.

Every integration is built around two ideas: pull context in, and push action out. Stripe pulls payment context. Linear pushes new issues out and surfaces status changes. HubSpot pulls CRM context. The goal is the agent never leaves the conversation.

What's available today

Five integrations are live. All are OAuth-based (or App install for GitHub) and all live at Settings → Integrations:

• [Stripe](/help/ochre/stripe-integration). Read-only via Stripe Connect. Plan, MRR, LTV, payment status on every ticket.
• [HubSpot](/help/ochre/hubspot-integration). Contact lifecycle, last contacted, company, owner. Live updates via webhook.
• [Linear](/help/ochre/linear-integration). Bidirectional. Convert ticket to Linear issue. Comments and status changes sync back to the conversation.
• [GitHub](/help/ochre/github-integration). GitHub App install. Convert ticket to GitHub issue. Two-way comment sync.
• [Slack](/help/ochre/slack-integration). Slack Connect channels routed into the inbox; outbound posts go out under your workspace's logo. See Per-workspace Slack branding.

That's the list. We get asked about Salesforce, Segment, and Confluence regularly. They're not shipped yet. We don't ship dishonest "coming soon" claims, so they're not in the product. If those matter to you, tell us.

How to think about which to install first

If you sell software with subscriptions, install Stripe first. The single highest-ROI piece of context is "is this customer paying us money, and how much." It changes how you triage every billing-related ticket.

If you have a sales motion, install HubSpot second. Lifecycle and owner context matters for routing and tone.

If your support team escalates engineering issues frequently, install Linear or GitHub (whichever your engineers actually use) third. Convert-to-issue is the killer feature, and the bidirectional sync means support knows the moment engineering closes the issue.

Slack last, unless you already have shared Slack channels with customers, in which case install Slack first.

Install patterns

Most integrations use OAuth: click connect, log in to the third-party service, authorize Ochre, done. GitHub is the exception: it's a GitHub App install (not user OAuth), which scopes access to specific repos.

All OAuth flows verify that return_to is on our domain (preventing open-redirect abuse) and use signed state for CSRF protection.

Token refresh is handled automatically. You don't need to think about it.

Permissions and storage

Each integration has scoped read or write access to only what we need. Stripe is read_only end-to-end: even if our token were leaked, no one could use it to make charges. Details for each integration are in Integration permissions.

Stored OAuth tokens are encrypted at rest and only readable through a server-side function that checks the caller is an Owner or Admin. Agent-role users cannot pull a token.

Disconnecting

Every integration can be disconnected from its detail page. Disconnecting clears the encrypted token and marks the integration as inactive. Some details vary by integration: see Disconnecting integrations.

What's next

Pick one. Start with Stripe integration if you bill customers, HubSpot integration if you have a sales motion, or Linear integration if your team escalates engineering issues constantly.