Intercom data source
Learn how to set up a Intercom data source and then move files data to one of the data destinations supported by Coupler.io.
2 steps to complete the setup
1. Set up your data source
1.1. Select the apps to connect: Intercom as a source and one of the available data destinations
1.2. Connect your Intercom account:
- Click Connect:
- You can select to share connection with the team. If you keep default (off) - connection will be private. Click Start:
- Sign in to your Intercom account via email & password or Google account
- Review accesses requested by the Coupler.io and click Authorize access:
- The account should be successfully connected
1.3. Select Intercom report type
Report types that do not support any filters:
- List of admins
- List of newsfeeds
- List of news items
- List of help center collections
- List of help centres
- List of ticket types
- List of teams
- List of tags
- List of subscription types
Report types that do not support date filters, however support advanced filters:
- List of companies
- List of segments
- List of data attributes
- List of articles
Report types that support date filters & advanced filters:
- List of tickets
- List of conversations
- List of contacts
1.4. Specify Report period date filter(s) (optional)
- Created after - use this filter to import only data entities created after specified date.
- Created before - use this filter to import only data entities created before specified date.
- Updated after - use this filter to import only data entities updated after specified date.
- Updated before - use this filter to import only data entities updated after specified date.
You can enter date in format YYYY-MM-DD or select it using calendar. You also can use macroses to define date dynamically.
1.5. Specify Advanced filters (optional)
Filters are different per each Report type.
List of articles (supports only "equal" operator)
| Key | Description and possible values | Example |
| phrase | The phrase within your articles to search for. Value: any string. |
phrase=Getting started |
| state | The state of the Articles returned. Value: one of published, draft or all. |
state=published |
| help_center_id | The ID of the Help Center to search in. Value: help center ID (integer). |
help_center_id=123 |
| highlight | Return a highlighted version of the matching content within your articles. Refer to the response schema for more details. Value: true or false |
List of companies (supports only "equal" operator)
| Key | Description and possible values | Example |
| tag_id | The id of the tag to filter by. |
tag_id=123 |
| segment_id | The id of the segment to filter by. |
segment_id=123 |
List of segments (supports only "equal" operator)
| Key | Description and possible values | Example |
| include_count | It includes the count of contacts that belong to each segment. Values: true or false |
include_count=true |
List of data attributes (supports only "equal" operator)
| Key | Description and possible values | Example |
| model | Data attribute model to return. Values: one of contact, company, conversation. |
model=company |
| include_archived | Include archived attributes in the list. By default we return only non archived data attributes. Values: true or false. |
include_archived=true |
List of tickets (supports different operators: equal, not equal, less than, greater than, contains, does not contain)
| Key | Description and possible values | Example |
| title | The phrase within your ticket title to search for. Value: string. |
title - equal - bug |
| description | The phrase within your ticket description to search for. Value: string. |
description - contains - issue |
| category | Category to filter ticket by. Value: one of Customer, Back-office, Tracker |
category - not equal - Customer |
| ticket_type_id | The id of the ticket type to filter by. |
ticket_type_id - equal - 5 |
| contact_ids | List of contacts id to filter by. |
contact_ids - equal - 65154ae5cb30a0e43e5e9111 |
| teammate_ids | List of teammates id to filter by. |
teammate_ids - not equal - 13434 |
| admin_assignee_id | The id of the admin to filter by. |
admin_assignee_id - equal - 13434 |
| team_assignee_id | The id of the team assignee to filter by. |
team_assignee_id - not - equal -34545 |
| open | Filter by status of the ticket - is it open or not. Values: true or false |
open - equal - true |
| state | Filter by ticket state. |
state - not equal - submitted |
List of conversations (supports different operators: equal, not equal, less than, greater than, contains, does not contain)
| Key | Description and possible values | Example |
| channel_initiated | Channel of conversation to filter by. Values: one of conversation, push, facebook, twitter , email. |
channel_initiated - equal - push |
| state | Filter by conversation state. |
state - equal - open |
List of contacts (supports different operators: equal, not equal, less than, greater than, contains, does not contain)
| Key | Description and possible values | Example |
| name | The phrase within your contact name to search for. Values: string. |
name - contains - Alex |
| role | Filter by contact role. Values: user or lead. |
role - equal - lead |
2. Set up your data destination
Continue setting up the integration depending on the tool you want to import data to. Select your tool from the list of supported data destinations and follow the relevant setup guide.