Learn more

Each data connector consists of an API call which you can configure behind the scenes. Fin will automatically choose when to use it and deliver a personalized answer to the customer.

You can connect any system which has an API; that might be your unique internal backend tool you have built for your business, or a third party app you're using like Shopify, Salesforce, Stripe, Jira, and more.

image

Connect to external systems

image

If you have one of the supported apps installed, you’ll see a template for this app listed under Create data connector. We currently support templates for Shopify, Stripe, and Statuspage (more on that below).

Create a data connector

From a 3rd party template

data connector templates are available when the following apps are installed in your workspace:

If the app is not already installed, go to the App Store to install. Once the app is installed, data connector templates for each app will appear as an data connector ready to set live.

When you click on a template, you’ll see some information about what the data connector does and you can test it in the Messenger preview. If you’re happy with the data connector behavior, just select Set live for AI Agent.

image

The Messenger preview here uses example data. When setting the data connector live, Fin will use your real customer data.

If you want to configure the data connector you can click on Customize, which will take you to the data connector builder for advanced configuration.

If you don’t have one of our supported apps installed, the apps will appear here for you to install them on your workspace. After installation, the relevant data connector templates will appear in the section above.

From an AI recommendation

You’ll see your unique AI recommended data connectors under "Create data connector from template". These are generated based on your conversation history to help you identify potential data connectors, see what percentage of conversation volume they could resolve, and preview them in the Messenger, before setting anything up.

For AI recommendations to appear, Fin needs to be live on your workspace and you must have sufficient conversation volume.

When you click on an AI recommended data connector, you’ll find information about what the data connector does and you can preview it in the Messenger (using example data). AI recommended data connectors are merely suggestions based on your conversation volume, but they require an API to be connected manually in order to work.

To set the data connector live, click Set up to configure the API details.

image

Now all you need to do is connect the data connector to your API by adding the HTTPS URL.

To further customize this data connector, see the custom data connector section below. 👇

From a custom data connector

image

Phase 1: API

This tab defines how Intercom communicates with your external system.

Identity

image

Give your connector a short, descriptive name — for example, "Get unpaid account balance." This helps Fin understand when to use it. Add an internal description for your team's reference.

Data inputs

Data inputs let you specify what information Fin needs to collect before the connector runs — for example, a customer's account number if it's not already stored in Intercom.

image

Click + Data input and choose a format:

Give each input a name and description so Fin knows how to collect it. You can also set a fallback value for cases where the API returns a null or missing response.

For each input, choose where the data comes from:

image

API endpoint

Add the HTTPS URL for your API and select the request method: GET, POST, PUT, DELETE, or PATCH.

image

Use the Attribute Inserter to pass dynamic values — like a customer's user ID — directly in the URL path or request body.

Authentication and headers

Select an authentication token and add any custom key-value headers your API requires (for example, Content-Type: application/json).

image

Once done, click Test connection to validate your setup before moving on.

image

Phase 2: Data

This tab controls how the API response is shaped before Fin uses it.

image

Restrict and shape

By default, Fin has access to the full API response. To limit what Fin can read, switch to Manually restrict access and select only the fields you want to expose.

Choose how you'd like to transform the response:

Object mapping

Map API response fields directly to Intercom objects to automate data syncing with your workspace.

Use Test code and Test connection to validate your logic before proceeding.

Phase 3: Fin

This tab determines how Fin interacts with the connector.

How should Fin use this connector?

Enabled (direct trigger)

Fin triggers the connector automatically based on the customer's question — no workflow required. Best for read-only connectors like "Check order status" and high-volume, repeatable queries.

image

You can control who this data connector is available to with reusable Fin audiences, or by creating a custom audience specifically for this connector. For example, you might make it available to customers in your "Enterprise plan" audience, or restrict it to a custom audience such as logged-in users with a verified email who ask about their account balance.

Disabled (manual trigger)

The connector won't run automatically. You'll need to add it manually to a Workflow, Task, Procedure, or Macro. Best for sensitive or write-active connectors — like "Delete account" — where you want human or workflow oversight before anything runs.

image

Use Fin preview to see exactly how Fin will respond using this connector before setting it live.

Phase 4: Security

The final step before going live. This tab handles access control for customer data.

image

Customer authentication

Toggle this on to enforce your workspace's authentication rules before the connector can access or display sensitive information. Authentication rules are configured at Settings > Workspace > Security > Customer authentication.

Security check

Run a diagnostic to assess the health and security of your API setup. Any risks are surfaced with actionable recommendations — resolve them before setting the connector live.

Once all checks pass, save your connector and set it live.

Rolling out data connectors

We recommend using audience rules to roll out data connectors in phases to your customer base. This enables you to validate the performance of the data connector and make tweaks/changes where necessary.

Monitor and manage

To find existing data connectors, navigate to Settings > Integrations > data connectors. Each row shows the connector name, status, general usage, Fin usage (including resolution rate and audience), health (success rate and overall indicator), security, and configuration details. Clicking a connector opens its health dashboard, where you can review usage, performance metrics, and execution logs, or open the configuration editor to make changes.

image

Viewing in the inbox

Go to the Inbox conversation and select Show conversation events. Events will show if Fin has access to the data connector and if the data connector is successfully triggered.

image

Inbox views can be created with the attribute “Fin AI Agent: Action used in reply”. This attribute is set if Fin calls an data connector and uses some or all of the response in an answer.

image

Versioning

Each data connector has a live version and a draft version. Edits are made to the draft without affecting the running live version.

Public APIs

Two public APIs give you programmatic access to data connector configurations and execution results. Full documentation is available in the Intercom Developer Hub.

Configuration API

The Configuration API is a set of CRUD endpoints for programmatically managing data connectors. Use it to implement new connectors, keep connectors in sync with your internal systems, and automate connector management at scale.

Method

Endpoint

Purpose

GET

/data_connectors

Returns a paginated list of all data connectors for the workspace, ordered by most recently updated first.

GET

/data_connectors/:id

Retrieves the full detail of a single data connector by ID, including configuration, data inputs, response fields, and object mappings.

POST

/data_connectors

Creates a new data connector in draft state. Configure its URL, headers, data inputs, and other settings, then set it live when ready.

PATCH

/data_connectors/:id

Updates an existing data connector. Only provided fields are changed. Set state to live or draft to change the connector's state.

DELETE

/data_connectors/:id

Deletes an existing data connector. The connector must be in draft state and must not be in use by any workflows or AI agents.

Authentication uses OAuth. Read and write access requires the read_write_data_connectors scope; read-only access requires the read_workflow_connector_execution_result scope.

Results API

The Results API gives you programmatic access to execution data for each data connector. Use it to build custom dashboards, feed alerting systems, or perform deeper analysis than the in-product health dashboard provides.

Filtering options include success status, specific error types, time ranges (Unix timestamps), and cursor-based pagination (up to 30 results per page). Authentication uses OAuth with the read_workflow_connector_execution_result scope.

Troubleshooting

Logs

For troubleshooting purposes, all response data generated from data connectors triggered by Fin is recorded for up to 14 days. You can access these logs under the specific data connector in Logs.

image

Data Connector Execution Webhook

For real-time signals on success and failure rates, you can use the Data Connector Execution Webhook. This can be useful to receive execution events from Intercom for creating real-time dashboards, alerts and SLA monitoring in your external services.


💡Tip

Need more help? Get support from our Community Forum Find answers and get help from Intercom Support and Community Experts


Related Articles

[

How to set up Data connectors for Workflows and Inbox

](https://www.intercom.com/help/en/articles/6298282-how-to-set-up-data-connectors-for-workflows-and-inbox)[

Using Data connectors for automation

](https://www.intercom.com/help/en/articles/6298285-using-data-connectors-for-automation)[

Setting up Data connectors authentication

](https://www.intercom.com/help/en/articles/6615543-setting-up-data-connectors-authentication)[

Fin and Data connectors FAQs

](https://www.intercom.com/help/en/articles/9916507-fin-and-data-connectors-faqs)[

How to use data connectors in Fin Procedures

](https://www.intercom.com/help/en/articles/13459820-how-to-use-data-connectors-in-fin-procedures)