Fin can reach your data warehouse. Read the warning first.

Fin reaches external systems through MCP connectors, and the list keeps growing. On September 8, 2026 Intercom's changelog added querying Snowflake data warehouses through an MCP connector. On September 11 it added connector templates for Stripe, Shopify and Statuspage.

The integration is the easy part. The part worth slowing down for is a sentence in Intercom's own help centre.

The sentence

Intercom writes: "We highly recommend exercising extreme caution with what tools are made available to Fin. Any data that is returned to Fin from a tool response may be shared with the customer."

Read that against a data warehouse. A warehouse is where the joins live. Lifetime value, margin, churn risk, the internal account notes, the fraud flags. A query written for an analyst returns columns an analyst is cleared to see. Fin is not an analyst, and the person on the other end of the conversation is not staff.

What this actually asks of you

It turns an integration ticket into a permissions design. Three decisions, none of them technical:

• What the connector's credential can read. Not what the warehouse contains. What this specific service account is scoped to. A read-only role over one curated view is a different risk from a role over the schema.
• Which fields can be spoken aloud. The safe pattern is a purpose-built view that contains only what a customer could be told directly, rather than filtering after the fact in Guidance.
• Who the connector is available to. Intercom supports audience rules on a connector, so it does not have to be live for every conversation while you are still learning what it returns.

How the connection is authenticated

Connections to third-party MCP servers use OAuth 2.0, and where a server supports it, a third-party access token can be stored in Intercom instead. Intercom's framing is that during the OAuth process you grant Fin specific permissions, and you are in control of what it can access.

That is accurate and it is also the whole point. The control exists. Somebody has to use it deliberately, at setup, before anyone is watching the transcript.

One correction worth making

Snowflake is not a one-click template. Intercom's help article on MCP connectors lists prebuilt templates for Linear, Stripe, Shopify and Zapier. The Snowflake capability arrived through the changelog and is reached as an MCP connection rather than picked from that template list. If your notes say otherwise, they are ahead of the documentation.

MCP also has to be enabled for your workspace before any of this appears.

The monitoring that makes it maintainable

Since September 10, connector health shows HTTP status codes charted over time alongside latency. That matters more than it sounds. A connector that starts returning errors does not announce itself in the inbox, it just quietly stops answering, and the first sign is usually a rise in escalations nobody can explain.

Put that chart somewhere a human looks weekly.

What we would do first

Build the curated view before building the connector. Decide what a customer may be told, express it as columns, point the credential at that and nothing else. Then turn the connector on for one segment and read the transcripts before widening it.

Connecting a warehouse to a customer-facing agent is not hard. Deciding what it is allowed to say is the work.

Verified against

• Intercom changelog, Snowflake querying through MCP, September 8, 2026, and data connector templates, September 11, 2026.
• Intercom changelog, data connector health tracking, September 10, 2026.
• Intercom help centre, Add MCP connectors for popular apps or custom MCPs, including the caution notice, the OAuth and token authentication methods, audience rules, and the template list.

Checked against Intercom's own documentation on September 13, 2026.