Which Intercom workspace does the connection use?

The workspace you are signed into when you authorize access. If your workspace is hosted in the EU or Australia, set **Data host region** at the bottom of the Intercom consent screen before you click **Authorize access**.

Can one pipeline load several objects at once?

No. A pipeline exports one object into one table. Create a separate pipeline for each object you need, each with its own table name.

Why is the Conversation Parts column empty?

Intercom returns the message-by-message history only when a single conversation is requested by its ID, so it is missing from the conversation list the pipeline reads. The Stats Count Conversation Parts parameter still provides the number of parts in each conversation.

What happens to records deleted in Intercom?

The destination table is replaced on every run, so it mirrors what the Intercom API returns at that moment. Records deleted in Intercom disappear from the table after the next run.

How do I get a custom attribute I just created in Intercom into my table?

Select the Custom Attributes field for the object. It loads as a JSON column that holds every custom attribute of the record, so a new attribute appears on the next run without any change to the pipeline. The Data Attributes object provides the definitions of those attributes: label, data type, and options.

Intercom

Renta exports eight Intercom objects to your data warehouse: contacts, companies, conversations, admins, teams, segments, tags, and data attributes.

You can flexibly configure the list of exported fields for each object. The integration automatically processes complex data structures:

Nested objects (such as geolocation) expand into flat columns.
Lists (such as tags and participants) are saved as nested records.
Dates are converted from the Unix timestamp format to a standard datetime format in the UTC timezone.

Authentication

Renta connects to Intercom through OAuth. You sign in to Intercom, review the requested permissions, and authorize the connection. You do not need to copy API keys or tokens manually.

Your credentials are encrypted in transit and at rest, and never stored in Renta's application database. You stay in control and can revoke access from your Intercom account settings at any time.

Connect Intercom source

Follow these steps to add Intercom as a source in Renta by authorizing access to your Intercom workspace.

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the Customer support category and click the Intercom card marked Source.

The category contains two Intercom cards. The one marked Destination is the reverse ETL connector that writes warehouse data back into Intercom.

Intercom Source card in the Customer support category of the Renta catalog

Start the authorizationStep 2

Click Log in to your Intercom account. Renta redirects you to the Intercom consent page.

Add a new Intercom connection page with the Log in to your Intercom account button

Grant access in IntercomStep 3

Review the permissions Renta requests. They cover the objects the connector reads: contacts, companies, conversations, teams and teammates, tags, and data attributes.
Check the Data host region value at the bottom of the screen and select the region where your workspace is hosted.
Click Authorize access.

You can revoke this access at any time in the list of authorized apps in your Intercom account.

Intercom consent screen with the permission list, the Authorize access button, and the Data host region selector

Name the connection and saveStep 4

In the Source name field, specify a name for this data source. It is used exclusively in the Renta interface.
Click Save.

The Access granted card shows the authorized Intercom account. The Re-authorize button next to it repeats the OAuth flow if you later need to switch the workspace.

Intercom connection setup with the source name field and the Save button

Source createdStep 5

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Intercom source in the Active status

Create a pipeline

Once the source is connected, create a pipeline to sync your Intercom data into your destination.

Create an Intercom pipeline

Link your Intercom source to a destination and configure the pipeline.

Select Intercom as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Intercom under Already connected and click Next step.

Select a source step with Intercom under Already connected

Select your Intercom connectionStep 2

Choose the Intercom connection you created earlier and click Next step. The card shows the account that authorized the connection.

Select your Intercom connection step with the authorized account shown on the connection card

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery under Already connected

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step.

Select your Google BigQuery connection step

Pipeline configuration

On the final step, choose the object, pick its fields, set the table name, and define the schedule.

Intercom objects

Select which Intercom object the pipeline exports. One pipeline loads one object into one table.

Object	Description
Admins	Teammates of the workspace: email, name, away-mode settings, inbox seat, and the teams they belong to.
Companies	Company records: name, the external company ID from your systems, plan, industry, size, monthly spend, session and user counts, custom attributes, segments, and tags.
Contacts	Users and leads: email, phone, role, owner, activity dates such as signed up and last seen, browser and location, custom attributes, tags, notes, and linked companies.
Conversations	Conversations with the message that started them, assignee, state, priority, rating, SLA, tags, participants, and the statistics block with reply, assignment, and close times.
Segments	Segments of the workspace: name, person type, and the dates the segment was created and updated.
Tags	The tag dictionary of the workspace: identifier and name of every tag.
Teams	Teams of the workspace together with the admins that belong to them.
Data Attributes	Definitions of the standard and custom attributes of contacts, companies, and conversations: label, data type, list of options, and whether the attribute is writable via API, Messenger, or the UI.

Fields

Select the Intercom fields to include in the destination table.

Use the search box to find a field by name, or click Select all. The Selected tab shows all selected fields, and the list below the picker lets you remove any of them.

Each object exposes the following fields.

Object	Fields
Admins	Type, ID, Email, Name, Away Mode Enabled, Away Mode Reassign, Has Inbox Seat, Team IDs
Companies	Type, ID, Company ID, Name, Created At, Updated At, Remote Created At, Last Request At, Monthly Spend, Session Count, User Count, Size, Website, Industry, Plan, Custom Attributes, Segments, Tags
Contacts	Type, ID, External ID, Email, Phone, Name, Role, Owner ID, Has Hard Bounced, Marked Email As Spam, Unsubscribed From Emails, Created At, Updated At, Signed Up At, Last Seen At, Last Replied At, Last Contacted At, Last Email Opened At, Last Email Clicked At, Custom Attributes, Browser, Browser Version, Browser Language, Operating System, Location City, Location Region, Location Country Name, Location Country Code, Location Continent Code, Tags, Notes, Companies
Conversations	Type, ID, Title, Created At, Updated At, Waiting Since, Snoozed Until, Source Type Extracted, Source Body Extracted, Source Subject Extracted, Source Delivered As Extracted, Source Author ID, Source Author Type, Source Author Email, Source Author Name, Contacts, Teammates, Admin Assignee ID, Team Assignee ID, Open, State, Read, Priority, SLA Applied, Conversation Rating, Tags, First Contact Reply Created At, First Contact Reply Type, First Contact Reply URL, Stats Count Assignments, Stats Count Conversation Parts, Stats Count Reopens, Stats First Admin Reply At, Stats First Assignment At, Stats First Close At, Stats First Contact Reply At, Stats Last Admin Reply At, Stats Last Assignment At, Stats Last Close At, Stats Last Closed By ID, Stats Last Contact Reply At, Stats Median Time To Reply, Stats Time To Admin Reply, Stats Time To Assignment, Stats Time To First Close, Stats Time To Last Close, Conversation Parts
Segments	Type, ID, Name, Created At, Updated At, Person Type
Tags	Type, ID, Name
Teams	Type, ID, Name, Admin IDs
Data Attributes	Type, ID, Model, Name, Full Name, Label, Description, Data Type, Options, API Writable, Messenger Writable, UI Writable, Custom, Archived, Created At, Updated At, Admin ID

Some of these columns come from nested blocks of the Intercom record. In Contacts, the location block splits into Location City, Location Region, Location Country Name, Location Country Code, and Location Continent Code. In Conversations, the source message (the Source fields), the first reply from a contact (the First Contact Reply fields), and the statistics block (the Stats fields) split the same way.

List fields remain nested. Tags, Segments, Contacts, Teammates, and Notes load as nested records with the identifier of each element and, where Intercom returns it, the name.

Custom Attributes loads as a JSON column with every custom attribute of the record, so adding an attribute in Intercom does not change the structure of the table. SLA Applied and Conversation Rating are JSON columns as well.

Date fields such as Created At, Updated At, Last Seen At, and the Stats timestamps arrive as UTC datetimes. Durations such as Stats Time To Admin Reply and Stats Median Time To Reply remain in seconds, as Intercom reports them.

The Conversation Parts column of the Conversations object is always empty. Intercom returns the message-by-message history of a thread only when a single conversation is requested by its ID.

Table name

Name the pipeline and the destination table.

Integration name.
The name of the pipeline. It is used exclusively in the Renta interface.
Table name.
The destination table name. You can keep the auto-generated name or enter your own.

Date range

Set the period the pipeline covers.

Date start.
The first date of the period.
Date end.
The last date of the period. Keep Today so that the end of the period advances with every run.

Intercom objects are snapshots of the current records, not statistics broken down by day. Renta loads every record of the selected object on each run, so the dates you set here do not limit the export.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

The new pipeline appears in the Pipelines section under the ETL tab, where you can monitor its runs, progress, and the destination table name.

Pipelines list with the new Intercom integration in the Completed status

Sync strategy

All Intercom objects synchronize the same way.

Strategy	Supported report types	Description
Full reload	Admins, Companies, Contacts, Conversations, Segments, Tags, Teams, Data Attributes	On every run Renta reads the complete list of records from Intercom and replaces the contents of the destination table, so the table mirrors the workspace at the time of the run. If the selected fields include a date, Renta partitions the destination table by the first such field, typically Created At.

Because every run reloads the whole object, the pipeline has no overwrite period setting. The volume of a run depends on how large your Intercom workspace is, not on how often the pipeline runs.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.