> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-deel.md).

# Integrating with Deel

Sync Deel workforce data into Drivetrain for headcount planning. Covers creating an organization token and choosing the read scopes to share.

Drivetrain uses organization token to integrate Deel, it enables user to limit the scopes they want to share.

[Prerequisites](#prerequisites)\
[Deel Setup](#deel-setup)\
[Create Organization Token](#step-1-create-organization-token)

## Prerequisites

1. An active Deel admin account.
2. Admin privileges in Drivetrain.

## Deel Setup

### Step 1: Create Organization Token

1. Log In into your Deel account and Click on **Hub,** on the next page Click on **Developer Center**

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-55531004a05206ee013e2f1459a4da252a0c9ad8%2FDeel-1.avif?alt=media)

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-b0bea8e05fdf027016dd302581ff19c2506de0ea%2FDeel-2.avif?alt=media)

2. On the Developer Center > API access & Sandbox and Click on **Generate New Token** under Organization Token

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-2101a946152e9867c9d133b0e1cb1159f2d60846%2FDeel-3.avif?alt=media)

3. Label the token as **Drivetrain Integration** and click on next

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-1b96d2f5939e7128e2a7d9ba5ae1b240292a6ac9%2FDeel-4.avif?alt=media)

4. Select the necessary scopes for for which you want to pull data into drivetrain, and choose the **read method** for every scope and click on **Generate**

{% hint style="info" %}
Scopes represent the objects user has created in their account, you can choose to not share certain scopes which doesn’t fit in the usecase. Please refer to [this](https://developer.deel.com/docs/scopes-1) to understand more about scopes
{% endhint %}

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-91f7661a79ba53ebfe8905fdd6478b8a02ae9cdd%2FDeel-5.avif?alt=media)

5. Copy the token in a secure place and click on close.

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-8bb7a688a101a4910b0dbe4d296459687675e623%2FDeel-6.avif?alt=media)

{% hint style="info" %}
That’s it share the organization token to your customer success manager.
{% endhint %}


---

# 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://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-deel.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.