> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# RD Station CRM as a destination

> Send your data from Nekt to RD Station CRM.

RD Station CRM is a sales management platform that helps businesses organize and track their sales pipeline. It provides tools for managing contacts, deals, organizations, and sales activities to improve conversion rates and revenue.

The RD Station CRM destination supports three operating modes:

* **Contacts** - creates or updates contacts in the CRM.
* **Deals** - creates or updates deals (sales opportunities) in the CRM.
* **Organizations** - creates or updates organizations (companies) in the CRM.

## 1. Add your RD Station CRM access

1. In the [Destinations](https://app.nekt.ai/destinations) tab, click on the "Add destination" button located on the top right of your screen. Then, select the RD Station CRM option from the list of connectors.

2. Click **Next** and you'll be prompted to add your access:

   * **Authorization**: Complete RD Station authorization to grant permissions for Nekt to load data into the CRM.
   * **Mode**: Select the operating mode for the connector:
     * **Create/Update Contacts** - maps your input table columns to contact fields and creates or updates contacts.
     * **Create/Update Deals** - maps your input table columns to deal fields and creates or updates deals.
     * **Create/Update Organizations** - maps your input table columns to organization fields and creates or updates organizations.
   * **Enable partial success**: Whether the connector should continue trying to sync records after one fails.

3. Click **Next**.

## 2. Select your data to send

1. The next step is letting us know which data you want to send. Select the layer and then the desired table.

   > Tip: The table can be found more easily by typing its name.

2. Click **Next**.

## 3. Map your columns

Map the columns from your input table to the corresponding RD Station CRM fields. The available destination fields depend on the mode you selected.

### Create vs. update behavior

If you map a column to the `_id` destination field, the connector performs an update (PUT) on the existing record with that ID. If no `_id` is mapped, the connector creates a new record (POST).

### Custom fields

RD Station CRM supports custom fields on contacts, deals, and organizations. Any destination field that is not in the standard fields list is automatically sent inside the `custom_fields` object in the API payload. Simply use the custom field slug as the destination field name (e.g., `cpf`, `erp_id`).

### Contacts mode

In contacts mode, each row in your input table represents a contact to create or update.

Available standard destination fields:

| Destination field | Description                                                         |
| :---------------- | :------------------------------------------------------------------ |
| `_id`             | CRM contact ID (for updates only)                                   |
| `name`            | Contact full name                                                   |
| `job_title`       | Contact job title                                                   |
| `birthday`        | Contact birthday (YYYY-MM-DD format)                                |
| `emails`          | Array of email objects (e.g., `[{"email": "...", "type": "work"}]`) |
| `phones`          | Array of phone objects (e.g., `[{"phone": "...", "type": "work"}]`) |
| `social_profiles` | Array of social profile objects                                     |
| `organization_id` | ID of the associated organization                                   |

Any other field (e.g., `cpf`, `erp_id`) is sent as a custom field.

**Example input table (contacts mode):**

| full\_name  | contact\_email                                | phone\_number     | cpf            |
| :---------- | :-------------------------------------------- | :---------------- | :------------- |
| Maria Silva | [maria@example.com](mailto:maria@example.com) | +55 11 91234-5678 | 111.111.111-11 |
| Joao Santos | [joao@example.com](mailto:joao@example.com)   | +55 21 99876-5432 | 222.222.222-22 |

Column mapping: `full_name` -> `name`, `contact_email` -> `emails`, `phone_number` -> `phones`, `cpf` -> `cpf`.

In this example, `cpf` is automatically sent inside `custom_fields` in the API payload.

### Deals mode

In deals mode, each row in your input table represents a deal to create or update.

Available standard destination fields:

| Destination field     | Description                                  |
| :-------------------- | :------------------------------------------- |
| `_id`                 | CRM deal ID (for updates only)               |
| `name`                | Deal name **(required for creation)**        |
| `status`              | Deal status (must be `ongoing` for creation) |
| `contact_id`          | ID of the associated contact                 |
| `organization_id`     | ID of the associated organization            |
| `stage_id`            | ID of the deal stage                         |
| `pipeline_id`         | ID of the sales pipeline                     |
| `owner_id`            | ID of the deal owner (user)                  |
| `campaign_id`         | ID of the associated campaign                |
| `expected_close_date` | Expected close date (ISO 8601 format)        |
| `rating`              | Numeric rating/classification                |
| `lost_reason_id`      | ID of the loss reason                        |

Any other field is sent as a custom field.

<Note>
  When creating deals, the `status` field must be set to `ongoing`. The RD Station CRM API only allows creating deals with this status.
</Note>

**Example input table (deals mode - create):**

| deal\_name     | org\_id                  | stage                    | amount |
| :------------- | :----------------------- | :----------------------- | :----- |
| Credito PJ 001 | 6621a1b2c3d4e5f678905678 | 6621a1b2c3d4e5f678900001 | 50000  |
| Credito PF 002 | 6621a1b2c3d4e5f678905679 | 6621a1b2c3d4e5f678900001 | 15000  |

Column mapping: `deal_name` -> `name`, `org_id` -> `organization_id`, `stage` -> `stage_id`, `amount` -> `valor_credito`.

In this example, `valor_credito` is automatically sent inside `custom_fields` in the API payload.

### Organizations mode

In organizations mode, each row in your input table represents an organization to create or update.

Available standard destination fields:

| Destination field | Description                            |
| :---------------- | :------------------------------------- |
| `_id`             | CRM organization ID (for updates only) |
| `name`            | Organization name                      |
| `owner_id`        | ID of the organization owner (user)    |
| `segment_ids`     | Segment IDs to associate               |

Any other field is sent as a custom field.

**Example input table (organizations mode):**

| company\_name    | company\_website                                       | cnpj               |
| :--------------- | :----------------------------------------------------- | :----------------- |
| Empresa ABC Ltda | [https://empresaabc.com.br](https://empresaabc.com.br) | 11.111.111/0001-11 |
| Tech Corp SA     | [https://techcorp.com.br](https://techcorp.com.br)     | 22.222.222/0001-22 |

Column mapping: `company_name` -> `name`, `company_website` -> `website`, `cnpj` -> `cnpj`.

In this example, both `website` and `cnpj` are automatically sent inside `custom_fields`.

## 4. Configure your RD Station CRM data destination

1. Describe your destination for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.

2. To define your [Trigger](https://docs.nekt.com/runs/scheduling-and-triggers), consider how frequently you need to have the data updated on the destination (every day, once a week, only at specific times, etc.).

3. Click **Done**.

### Check your new destination!

1. Once completed, you'll receive confirmation that your new destination is set up!

2. You can view your new destination on the [Destinations](https://app.nekt.ai/destinations) page. Now, for you to be able to see it on RD Station CRM, you have to wait for the pipeline to run. You can monitor it on the [Destinations](https://app.nekt.ai/destinations) page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your data should be seen on RD Station CRM.

> If you encounter any issues, reach out to us via Slack, and we'll gladly assist you!