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

# RD Station CRM

> Sync contacts and companies both ways with RD Station CRM, keep owners, stages, tasks and notes on each contact's deal, and send WhatsApp templates when something changes in RD Station.

The RD Station CRM integration keeps your contacts in step between RD Station CRM and Ciarem. RD Station contacts become Ciarem contacts that templates, the AI and the Inbox can use, and what your team changes in Ciarem reaches RD Station. Each contact's owner, funnel stage, tasks and conversation notes live on its deal in RD Station, and rules in Ciarem can send a WhatsApp template when a deal or a contact changes there. Admins set it up under **Settings > Integrations > RD Station CRM**.

Ciarem works with one CRM at a time: you can connect HubSpot, Attio or RD Station CRM, only one of them. To switch, disconnect the one you have first.

## Plans

RD Station CRM is included on **Growth** and **Scale**, and during the free trial. It is not included on **Solo**. Solo can't be chosen while RD Station CRM is connected: disconnect it first, or pick Growth or Scale. See [Plans and billing](https://help.ciarem.ai/billing/plans-and-billing.md).

If your trial ends or your subscription stops, RD Station CRM stays connected but nothing syncs in either direction and no rule sends. Once you subscribe to Growth or Scale, syncing resumes on its own. A contact you edited in Ciarem while sync was stopped reaches RD Station the next time it changes.

## Connect RD Station CRM

**1. Open the RD Station CRM integration**

Go to **Settings**, then **Integrations**, and click **Connect** on the RD Station CRM card.

**2. Approve access in RD Station**

Sign in to RD Station and approve access for Ciarem. RD Station shows the permissions Ciarem gets.

**3. Finish setting up RD Station CRM**

Back in Ciarem, a three-step setup asks for your field mapping, your import filters, and your funnel and deals. Click **Finish** to save it and start the sync. Nothing syncs until you finish, so your choices apply from the very first contact.

If you close the setup, the integration shows **Partially configured**. Click **Finish setup** to come back to it. After setup, change any of it on the **Field mapping**, **Import filters** and **Funnel and deals** tabs, then click **Save changes**. Rules, on the **Rules** tab, save one by one.

## While RD Station CRM is connected

Unlike HubSpot and Attio, the **Contacts** and **Companies** pages stay in Ciarem: your team keeps working with contacts and companies here, and what they change is written to RD Station. In the Inbox, a conversation's details panel shows the **Last RD Station sync** and a **View in RD Station** link. A company linked to RD Station has a **View in RD Station** link too.

## What syncs

* **Contacts, both ways.** An RD Station contact is imported once it has a valid phone number with its country code. RD Station keeps phones as they were typed, so a number with no country code, like (11) 98888-7777, is listed under [Contacts not imported](#contacts-not-imported) until you add one. A contact created or edited in Ciarem is written to RD Station (name, email and phone) once it has a name and a phone or an email. When a contact has several emails or phones, Ciarem uses the first email and the first valid phone. When Ciarem writes an email or phone to RD Station, it adds it to the contact's list and never removes the others.
* **No duplicates from Ciarem.** RD Station accepts several contacts with the same phone or email. So before creating one, Ciarem looks for a contact in RD Station with the same phone, then the same email, and links to it. If it finds more than one, it picks none and lists the contact under [Not sent to RD Station](#not-sent-to-rd-station).
* **Synced automatically.** Name, email and phone sync on every contact without any mapping. RD Station has one name field: Ciarem splits it into first and last name at the first space.
* **Field mapping.** On the **Field mapping** tab, pick RD Station custom fields to bring into Ciarem contact properties, so templates and the AI can use them. Choose a Ciarem property for each, or **Create from RD Station** to make a matching one. Mapped fields sync from RD Station to Ciarem only. Text, link, CPF and CNPJ fields become text properties; number, currency and percentage become numbers; dates stay dates; single choice and multiple choice become single and multiple selection. Every mapped property needs a **Description for the AI**: the AI learns from it what the property means and when to use it, so phrase it as an instruction.
* **Import filters.** On the **Import filters** tab, add conditions to choose which contacts are imported. Only contacts that meet every condition are added. With no filters, every contact with a valid phone number is imported. Contacts already in Ciarem keep syncing.
* **The contact's deal.** In RD Station a contact has no owner or stage of its own: the owner, the stage, tasks and notes belong to a deal. So each synced contact gets one deal in the pipeline you pick, which carries them. Ciarem uses an open deal RD Station already has for the contact. When a contact with no open deal gets an owner, moves stage or gets a task in Ciarem, Ciarem opens one, named after the contact. Turn off **Create deals from Ciarem** if your own automation creates deals. A contact imported from RD Station that never needs a deal never gets one, so connecting doesn't fill your pipeline.
* **Default deal owner.** Picked on the **Funnel and deals** tab. It owns the deals Ciarem opens for contacts whose owner isn't an RD Station user, and creates or completes tasks for teammates who aren't. It is required while **Create deals from Ciarem** or **Sync tasks** is on.
* **Contact owner.** The deal's owner and the contact's owner sync both ways, for teammates whose email is an RD Station user. An RD Station user with no teammate of the same email leaves the Ciarem owner as it was, and a teammate who isn't an RD Station user leaves the deal's owner as it was. The **Funnel and deals** tab counts the RD Station users with no teammate.
* **Funnel stages.** On the **Funnel and deals** tab, pick an RD Station pipeline. Its stages become your stages in Ciarem. RD Station owns them and their order, so you add, rename or reorder them in RD Station; changes there reach Ciarem with the daily sync. Describe each stage so the AI knows when a contact belongs there. To let the AI move contacts into a stage, click the **AI off** button next to it (every stage but the first) and choose which agents may move contacts there and when. A stage change on either side moves the contact's deal or the contact. The Playground only shows the move; it doesn't write it. A deal marked won, lost or paused in RD Station is no longer the contact's deal: the contact keeps its stage, and its next open deal takes over, or Ciarem opens a new one when it needs one. Until you pick a pipeline, funnel stages are off and owners, tasks and notes don't sync. Switching to another pipeline later replaces your stages with its stages, places contacts again from their deals there, and removes the AI settings of the current stages.
* **Tasks, both ways.** **Sync tasks** (on the **Funnel and deals** tab) is on unless you turn it off. While it is on, a contact's [tasks](https://help.ciarem.ai/using-ciarem/tasks.md) and the tasks on its deal stay in step: title, note, due date, type and completion. A task for a contact with no deal opens one, unless **Create deals from Ciarem** is off; then the task stays in Ciarem only. A task deleted in Ciarem is canceled in RD Station (one already completed there stays as history), and one canceled in RD Station is deleted in Ciarem. Only open tasks are linked: finished tasks are neither imported nor sent. A task Ciarem creates in RD Station is assigned to the contact's owner when that teammate is an RD Station user, otherwise to the default deal owner; changing the assignee in RD Station doesn't come back. Priority doesn't sync. RD Station's email and WhatsApp tasks arrive as messages, and lunches and visits as meetings.
* **Notes on the deal.** Two things leave a note on the contact's deal, in your organization's language: a resolved conversation (the channel, the AI summary, who resolved it and a link to the conversation) and a WhatsApp template sent to one contact (the template, the line, who sent it and a link). Broadcasts leave no note, and neither does a conversation the customer never wrote in. A note never opens a deal, so a contact with no deal gets none. Notes written in RD Station don't come to Ciarem.

## Companies

Companies sync with RD Station organizations too, once two things are in place:

1. **Turn on the Companies add-on** under **Settings > Add-ons**. See [Companies](https://help.ciarem.ai/using-ciarem/companies.md).
2. **Finish the RD Station CRM setup.** Nothing to reconnect: if RD Station CRM was already connected, companies start syncing on their own within a few minutes of the add-on being on.

The **Companies** page stays in Ciarem, and **Link contacts by email domain** keeps working, because RD Station doesn't link contacts by domain itself.

* **Name, website and owner, both ways.** Every RD Station organization is imported with its name and website, and its owner when that RD Station user is a teammate. Other company fields stay in Ciarem only. RD Station keeps a website as it was typed, so Ciarem compares the domain: `https://acme.com/contato` and `acme.com` are the same. If the domain already belongs to another company in Ciarem, it is left as it was.
* **Matching.** An organization is matched to a Ciarem company by its domain, then by its name. A Ciarem company is looked up in RD Station by name before it is created there.
* **A contact's organization.** The organization on an RD Station contact is that contact's **primary company** in Ciarem, and the other way round: when you make another company primary in Ciarem, it becomes the contact's organization in RD Station. RD Station holds one organization per contact, so other companies you link to a contact stay in Ciarem only. A link the AI or the email domain made reaches RD Station only after a person confirms it.
* **What reaches RD Station.** A company the AI or the email domain created reaches RD Station only once a person edits it or confirms a link to it. A new organization in RD Station needs an owner: the company's owner when that teammate is an RD Station user, otherwise the default deal owner. With neither, the company isn't created in RD Station.
* **Removing a primary company.** RD Station can't remove a contact's organization through its API. When you remove a contact's primary company in Ciarem, Ciarem stops reading it back for that contact, but RD Station keeps showing it until you remove it there too.
* **Names are unique.** RD Station refuses two organizations with the same name. A company renamed in Ciarem to a name RD Station already has keeps its old name there; its other changes still reach RD Station.
* **Deleting an organization in RD Station.** The company stays in Ciarem with its fields and is never sent back; the contact links that came from RD Station are removed. A company that is still linked to RD Station can't be deleted in Ciarem while RD Station CRM is connected: delete it in RD Station instead.

## Send WhatsApp when something changes in RD Station

RD Station's own automations send WhatsApp only through RD Station's own product, and RD Station has no way for other apps to add steps there. So the rules live in Ciarem: on the **Rules** tab, each rule says "when this happens in RD Station, send this approved template from this WhatsApp line". Turn a rule off with its switch, or edit and delete it. An organization can have up to 50 rules.

| When | It fires when |
| - | - |
| A deal enters a stage | A deal the contact already had moves to that stage of your pipeline. A deal created in that stage counts as created, not as entering it |
| A deal is won | The contact's deal is marked won |
| A deal is lost | The contact's deal is marked lost |
| A deal is created | A new deal in your pipeline becomes the contact's deal |
| A contact is created in RD Station | A contact created in RD Station becomes a new Ciarem contact. A contact that matches one Ciarem already had, by phone or email, doesn't count |
| A contact field changes to a value | A single choice field, mapped on the **Field mapping** tab, takes the option you chose |

* **Only changes made in RD Station fire a rule.** A change made in Ciarem, by your team or the AI, never does, and neither do the first import, the daily sync or a contact or deal Ciarem created. A change that reaches Ciarem more than 24 hours late doesn't send either.
* **Deal rules work on the pipeline you picked**, for deals linked to a synced contact. Until you pick a pipeline they can't be chosen.
* **The template fills itself.** Its variables are filled from the contact, like `{{contact.first_name}}` or `{{company.name}}`. A template that needs a value typed for each send, such as a coupon or the end of a link, can't be used in a rule.
* **One send per change.** RD Station can report one change several times; the rule still sends once.
* **The result goes on the deal.** A sent template leaves the same note on the deal as a template your team sends. When it isn't sent, the note says why: no WhatsApp number, template unavailable, missing variables, messaging limit reached, opted out of marketing, insufficient balance, or send failed. A contact rule writes its note on the contact's deal, and none when the contact has no deal. A contact with no WhatsApp number is sent nothing and nothing is charged.
* **A rule with a warning doesn't send.** When the stage, the pipeline, the field, the option, the template or the line a rule uses is gone or changed, the rule shows a warning saying which. Edit the rule to fix it.

## Contacts not imported

Some RD Station contacts can't be created in Ciarem. Once setup is done, the **Not imported** tab lists them under **Contacts not imported**, each with the reason:

* **Phone already used**: another contact in Ciarem already has this phone number.
* **Email already used**: another contact in Ciarem already has this email.
* **Invalid phone**: the contact's phone isn't a number Ciarem can use. Add the country code, for example +55.

A contact with no phone at all isn't imported and isn't listed here: add a phone in RD Station and it's imported.

Fix the contact in RD Station, for example by correcting the value, and it syncs on its own.

## Not sent to RD Station

The same tab lists, under **Not sent to RD Station**, the Ciarem contacts RD Station refused, each with the reason and a link to the contact:

* **Contact refused** or **Deal refused**: RD Station refused the contact or its deal, with RD Station's own explanation.
* **Phone on several RD contacts** or **Email on several RD contacts**: Ciarem found more than one RD Station contact with this phone or email and didn't pick one. Fix the duplicates in RD Station.
* **RD contact linked to another contact**: the matching RD Station contact is already linked to another Ciarem contact.

Fix the contact and it is sent again the next time it changes in Ciarem.

## Deleting a contact or a deal in RD Station

Deleting a contact in RD Station unlinks it from Ciarem. The Ciarem contact and its conversations are kept.

Deleting a deal in RD Station unlinks it from the contact, which keeps its owner and stage in Ciarem. The contact's next open deal takes over, or Ciarem opens a new one the next time it needs one.

## A deleted pipeline

If the pipeline you picked is deleted in RD Station, the integration shows **Pipeline missing** and the **Funnel and deals** tab asks you to pick another. Until you do, contacts keep syncing, but owners, stages, tasks and notes don't, and deal rules show a warning.

## Reconnect

If RD Station stops accepting Ciarem's access, the integration shows **Needs reconnection**. Click **Reconnect** and approve access again. Choose the same RD Station account to keep your setup and your links. Choosing a different account starts over: the old account's contact and company links are removed, and the setup asks to be finished again.

## Disconnect

**Disconnect** stops the sync and the rules. Your contacts, companies, their conversations and your funnel stages stay in Ciarem. Your sync settings are cleared, so connecting again runs the setup again; choosing the same account keeps contacts linked to theirs. Your data in RD Station CRM is not touched.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.