Data connector templates let you install a pre-built, ready-to-use Data connector from a catalog of templates grouped by app. Templates are automatically configured for you using your installed integrations, so they're ready to test and set live instantly — and as Intercom improves them over time, you're notified and can review any changes before applying them.

To use these templates, go to Settings > Integrations > Data connectors, click New, and choose Start from a template. You'll see templates grouped by app — select the template you want to install.

The template catalog shows all available pre-built templates grouped by app (for example, Stripe, Shopify, and Statuspage). Browsing and installing is built into the new connector flow — select Start from a template when creating a connector, choose your app, and pick the template you want.

Installing a template creates an independent copy in your workspace. You can customize it freely without affecting the original template or other workspaces.

When Intercom publishes an improved version of a template you've already installed, your connector is not automatically changed. Instead, you're notified that a newer version is available. You can review exactly what changed before deciding whether to apply the update — and any customizations you've made to your connector are preserved.

Each installed connector records which template version it came from, so it's always clear whether your connector is up to date or has a newer version available.

When you set up these Data connectors, Fin can fully resolve requests from customers who want to get information from your Shopify Storefront. This uses your existing Shopify integration, so there’s no additional connections that you need to make with another tool.

Simply set these Data connectors live using the preset conditions, or set your own conditions to tell Fin what requirements must be met before getting information from Shopify.

Use these Data connectors to:

Use to search the store's catalog with the customer's own words. Returns the matching products with their price range, availability, image, and store link.

Use to read the contents of a customer's Shopify cart. Returns every line in the cart with its quantity, the product and variant it refers to, per-line and cart totals, and the checkout link.

Use to change the quantity of an item already in the customer's Shopify cart. Returns the updated cart with every line, the new totals, and the checkout link. Example customer queries include:

This action requires the cart_id, the line_id of the item to change, and the new quantity. The line_id is the cart line ID returned by the Get Shopify cart action, not the product or variant ID, so read the cart first to resolve which line the customer means. Setting quantity to 0 removes the line entirely, so this action covers both changing a quantity and removing an item. It replaces those halves of the deprecated update_cart tool on the Shopify Storefront MCP endpoint; adding a new item is a separate Storefront mutation.

Use to look up one product in the store's catalog — its description, price range, availability, image, and every purchasable variant with that variant's own price, SKU, options and stock. Use this when the customer asks about a product rather than about their cart or an order.

Use to get details about the customer's orders and help troubleshoot any order related issues. This action will provide all the orders details for the customer like order status, items purchased, shipping address, tracking information, or other relevant order details.

When you set up this Data connector, Fin can fully resolve requests from customers reporting or asking about an incident you've recorded on Statuspage. This uses your existing Statuspage integration, so there’s no additional connections that you need to make with another tool.

Simply set the Data connector live using the preset conditions, or set your own conditions to tell Fin what requirements must be met before getting information from Statuspage.

Use when a customer is experiencing an issue to check if there are any ongoing system outages, service disruptions, or unresolved incidents that could explain the disruption the customer is facing. This action will provide all the active incidents, their status, and the latest update.

When you set up these Data connectors, Fin can fully resolve requests from customers who need information stored in Stripe. This uses your existing Stripe integration, so there’s no additional connections that you need to make with another tool.

Simply set these Data connectors live using the preset conditions, or set your own conditions to tell Fin what requirements must be met before getting information from Stripe.

Use these Data connectors to:

Retrieves a single Stripe customer by their Stripe customer id (cus_...). Surfaces the customer's stored details — id, email, name, balance, currency, delinquency and creation date. Read-only.

Returns a list of your Stripe customers, optionally filtered by exact email match. Surfaces each customer's stored details — id, email, name, balance, currency, delinquency and creation date. Read-only.

Lists a Stripe customer's invoices (most recent first, up to 10) — invoice id, status, amount due, amount paid, currency, billing period and the hosted invoice URL. Pass the customer's Stripe id (cus_...). Read-only.

Searches a Stripe customer's charges (up to 10) — charge id (ch_...), amount, currency, status, paid and refunded flags, description and creation date. Pass the customer's Stripe id (cus_...). Commonly used to find the charge_id needed before issuing a refund. Read-only.

Searches your Stripe customers by exact email address and returns the matching customers — id, email, name, balance, currency, delinquency and creation date. This is the most common starting point for a Stripe lookup when you only have the customer's email. Read-only. Fin uses this connector to pull up someone's Stripe records by email. If the email field isn't protected from unverified updates, a customer could change it in the Messenger and pull up someone else's records instead. Check the security tab in your data connector draft and make sure email is a protected field.

Use to get details about the customer’s subscriptions and help troubleshoot any subscription related issues. This action will provide all subscription information for the customer like subscription status, billing frequency, next billing date, or plan details.

Example customer queries include: