> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/intercom/synchronize-companies.md).

# Synchronize companies

## Overview

In this destination service, DinMo will export and update attributes in the companies table, and, optionally, insert new company records.

To do so, you will need to go through these three steps:

* Creating an Intercom destination. Refer to the [corresponding section](#destination-setup) for more info.
* Creating a custom segment or custom model composed of all the companies records and their attributes that will be updated in Intercom. Refer to this [step-by-step tutorial](/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo/create-your-first-segment.md) to learn how to build segments without SQL in DinMo.
* Activating the segment or model to the Intercom destination to start sending data. Refer to the [corresponding section](#activation-configuration) for more info.

Each time the activation will be running:

* If you ticked the insert mode option, all new companies records in the segment or model will be inserted as a new company in Intercom
* All attributes values that have changed since the last activation will be updated in Intercom

If you chose not to insert new companies, only records of the segment or model who have an identifier linked to an Intercom company will be updated.

**Note:** Only company records which are linked to existing Intercom contacts will be displayed in the Intercom interface.

## Destination setup

To start synchronizing companies, you are first required to create an Intercom destination with the corresponding destination service.

{% hint style="info" %}
Learn how to create such a destination in our[ step-by-step tutorial](/guides/get-started-with-dinmo/initial-configuration-of-dinmo/create-a-destination.md)
{% endhint %}

## Activation configuration

Once the destination has been setup, and your DinMo segment created, you can create an activation to start sending data to Intercom right away.

{% hint style="info" %}
Learn how to activate a segment in our [step-by-step tutorial](/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo/activate-your-first-segment.md)
{% endhint %}

### Fields mapping

In the Fields mapping section, you are asked to specify the field contained in your DinMo segment corresponding to company ID. This field will be used to link the segment's records to existing company records in Intercom.

You can then map any other attribute existing in Intercom. These attributes will then be updated by DinMo during each activation. Non mapped attributes will not be modified by DinMo.

### Custom Attributes

In this section, any field you select will be exported as a new custom attribute in Intercom. The associated field will have the same name in Intercom and DinMo.

The values of the attributes selected here will then also be updated at each activation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dinmo.io/integrations/destination-platforms/intercom/synchronize-companies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.