> 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/zendesk/synchronize-users.md).

# Synchronize users

## Overview

In this destination service, DinMo will export and update attributes attached to your users.

Optionally, new users can be as well imported in this destination service.

To create such an activation, you will need to go through these three steps:

* Creating a Zendesk destination. Refer to the [corresponding section](#destination-setup) for more info.
* Creating a user segment composed of all the records and their attributes that will be updated in Zendesk. 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 to the Zendesk 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 users in the segment will be inserted in Zendesk
* All attributes values that have changed since the last activation will be updated in Zendesk

If you chose not to insert new contacts, only records of the segment which are already present in Zendesk will be updated.

## Destination setup

To start synchronizing objects, you are first required to create a Zendesk 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 Zendesk 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

You need to decide which information DinMo will use to reconcile the segment's data with Zendesk users. If you opt to match users using their email addresses, it means DinMo will recognize Zendesk users by their email addresses.

You must then choose to map the corresponding field under the fields mapping section. Zendesk API also requires to receive the Name of the users you send.

You can then map any other attribute existing in Zendesk. These attributes will then be updated by DinMo during each activation.

### Custom Attributes

In this section, any field you select will be exported as a new custom attribute in Zendesk. The associated field will have the same name in Zendesk 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/zendesk/synchronize-users.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.