RD Station CRM

Creating the data source

How to connect

In Kondado, add a new RD Station CRM data source.
Click Continue: you will be redirected to RD Station to sign in to your account.
Sign in with your RD Station CRM user and, if the account has more than one RD product, choose RD Station CRM.
Authorize Kondado's access. You are sent back to Kondado with the data source saved.
Done: now create the integrations you need.

Important

We recommend authorizing with a user that has the administrator profile in RD Station CRM.
Kondado only reads your data. Nothing is created or changed in your CRM.
There is no token to generate or copy: Kondado renews the authorization automatically. If it is revoked in RD Station, just edit the data source and authorize again.

Pipelines

Summary

Campaigns
Companies
Contacts
Custom fields
Deals
Deals: notes
Deals: products
Lost reasons
Meetings
Products
Sales pipelines
Sales pipelines: stages
Segments
Sources
Tasks
Teams
Users

Relationship chart

Click to expand

Campaigns

This pipeline is free

Replication type: Full

Campaigns registered in RD Station CRM. Each deal can be linked to a campaign, which allows measuring the return of each marketing action.

Field	Type
id	text	[en] Campaign identifier.
name	text	[en] Campaign name.
description	text	[en] Campaign description.
created_at	timestamp	[en] Timestamp when the campaign was created.
updated_at	timestamp	[en] Timestamp of the last update of the campaign.

Companies

Replication type: Incremental or Full (user configurable)

Parameters:

Read start date (Savepoint): Initial date to replicate data

Relationships:

owner_id → Users > id
segment_ids → Segments > id
follower_ids → Users > id

Companies (organizations) registered in RD Station CRM, with address, owner, segments and custom fields.

Field	Type
id	text	[en] Company identifier.
name	text	[en] Company name.
description	text	[en] Company description.
url	text	[en] Company website.
address_line	text	[en] Company address.
address_latitude	float	[en] Latitude of the company address.
address_longitude	float	[en] Longitude of the company address.
owner_id	text	[en] Identifier of the user who owns the company. Users > > id
segment_ids	text	[en] Comma-separated identifiers of the company segments. Segments > > id
follower_ids	text	[en] Comma-separated identifiers of the users following the company. Users > > id
custom_fields	text	[en] All of the company custom fields, as JSON. The following columns bring each custom field separately.
created_at	timestamp	[en] Timestamp when the company was created.
updated_at	timestamp	[en] Timestamp of the last update of the company.

Contacts

Replication type: Incremental or Full (user configurable)

Parameters:

Read start date (Savepoint): Initial date to replicate data

Relationships:

organization_id → Companies > id

Main object

Contacts (people) registered in RD Station CRM. E-mails, phones, social profiles and legal bases live in the related tables.

Field	Type
id	text	[en] Contact identifier.
name	text	[en] Contact name.
job_title	text	[en] Contact job title.
whatsapp_username	text	[en] Contact WhatsApp username.
birthday	date	[en] Contact birthday.
organization_id	text	[en] Identifier of the company the contact belongs to. Companies > > id
context_origin	text	[en] Origin of the contact record within RD Station CRM.
custom_fields	text	[en] All of the contact custom fields, as JSON. The following columns bring each custom field separately.
created_at	timestamp	[en] Timestamp when the contact was created.
updated_at	timestamp	[en] Timestamp of the last update of the contact.

rdstationcrm_v2_contacts_emails

E-mails of RD Station CRM contacts. A contact can have more than one e-mail, and each becomes a row in this table.

Field	Type
contact_id	text	[en] Identifier of the contact who owns the e-mail.
email	text	[en] Contact e-mail address.

rdstationcrm_v2_contacts_phones

Phone numbers of RD Station CRM contacts. A contact can have more than one phone, and each becomes a row in this table.

Field	Type
contact_id	text	[en] Identifier of the contact who owns the phone number.
phone	text	[en] Contact phone number.
type	text	[en] Phone type: work, fax, home or mobile.

rdstationcrm_v2_contacts_social_profiles

Social network profiles of RD Station CRM contacts.

Field	Type
contact_id	text	[en] Identifier of the contact who owns the social profile.
type	text	[en] Social network of the profile: facebook, linkedin or skype.
username	text	[en] Contact username on the social network.

rdstationcrm_v2_contacts_legal_bases

Legal bases (Brazilian GDPR) recorded for RD Station CRM contacts.

Field	Type
contact_id	text	[en] Identifier of the contact who owns the legal basis.
category	text	[en] Category of the legal basis for processing the contact's data.
type	text	[en] Type of the legal basis.
status	text	[en] Status of the legal basis (for instance, whether consent is still valid).

Custom fields

This pipeline is free

Replication type: Full

Main object

Catalog of the custom fields created in the RD Station CRM account. Use the slug column to join with the custom field columns of the deals, contacts, companies and products tables.

Field	Type
id	text	[en] Custom field identifier.
name	text	[en] Custom field name, as shown in the RD Station CRM screen.
slug	text	[en] Custom field key. It is the key under which the field shows up in the deals, contacts, companies and products tables.
entity	text	[en] Object the custom field belongs to: deal, contact, organization or product.
type	text	[en] Custom field type: text, date, option, multiple_choice, cpf, cnpj, phone, number or hyperlink.
options	text	[en] Comma-separated available options of the field. Filled in only for the option and multiple_choice types.
is_unique	boolean	[en] Indicates whether the field rejects values already used by another record.
allow_new_option	boolean	[en] Indicates whether the user can create new options while filling in the field.
display_order	int	[en] Position of the field in the RD Station CRM screen.
required_rules	text	[en] Rules that make the field mandatory, as JSON.
display_rules	text	[en] Rules controlling when the field is displayed, as JSON.
created_at	timestamp	[en] Timestamp when the custom field was created.
updated_at	timestamp	[en] Timestamp of the last update of the custom field.

rdstationcrm_v2_custom_fields_options

Available options of each RD Station CRM custom field: one row per option. Equivalent to the options column of the custom fields table, in a shape suitable for joining and counting.

Field	Type
custom_field_id	text	[en] Custom field identifier.
option	text	[en] One of the available options of the custom field.

Deals

Replication type: Incremental or Full (user configurable)

Parameters:

Read start date (Savepoint): Initial date to replicate data

Relationships:

pipeline_id → Sales pipelines > id
stage_id → Sales pipelines: stages > id
owner_id → Users > id
source_id → Sources > id
campaign_id → Campaigns > id
lost_reason_id → Lost reasons > id
organization_id → Companies > id
contact_ids → Contacts > id
contact_id > _kdd_contacts → Contacts > id

Main object

Deals (sales opportunities) registered in RD Station CRM, with amounts, pipeline, stage, owner and custom fields.

Field	Type
id	text	[en] Deal identifier.
name	text	[en] Deal name.
status	text	[en] Deal status: won, lost, ongoing or paused.
rating	int	[en] Deal rating, from 1 to 5 stars.
one_time_price	float	[en] One-time (non-recurring) deal amount.
recurrence_price	float	[en] Recurring deal amount.
total_price	float	[en] Total deal amount, summing the one-time and the recurring amounts.
expected_close_date	date	[en] Date on which the deal is expected to close.
closed_at	timestamp	[en] Timestamp when the deal was closed (won or lost).
pipeline_id	text	[en] Identifier of the sales pipeline the deal belongs to. Sales pipelines > > id
stage_id	text	[en] Identifier of the deal's current stage within the pipeline. Sales pipelines: stages > > id
owner_id	text	[en] Identifier of the user who owns the deal. Users > > id
source_id	text	[en] Identifier of the deal source. Sources > > id
campaign_id	text	[en] Identifier of the campaign associated with the deal. Campaigns > > id
lost_reason_id	text	[en] Identifier of the lost reason, filled in when the deal is lost. Lost reasons > > id
organization_id	text	[en] Identifier of the company linked to the deal. Companies > > id
contact_ids	text	[en] Comma-separated identifiers of the contacts linked to the deal. Contacts > > id
distribution_settings	text	[en] Deal distribution settings, as JSON.
custom_fields	text	[en] All of the deal custom fields, as JSON. The following columns bring each custom field separately.
created_at	timestamp	[en] Timestamp when the deal was created.
updated_at	timestamp	[en] Timestamp of the last update of the deal.

rdstationcrm_v2_deals_contacts

Link between RD Station CRM deals and contacts: one row per contact of each deal. Equivalent to the contact identifiers column of the deals table, in a shape suitable for joining with the contacts table.

Field	Type
deal_id	text	[en] Deal identifier.
contact_id	text	[en] Identifier of the contact linked to the deal. Contacts > > id

Field

Type

deal_id

text

[en] Deal identifier.

contact_id

text

[en] Identifier of the contact linked to the deal.

Contacts > > id

Deals: notes

Replication type: Incremental with update window or Full (user configurable)

Parameters:

Update window (days): How many days previous to the savepoint the records will still be replicated
Read start date (Savepoint): Initial date to replicate data

Relationships:

deal_id → Deals > id
user_id → Users > id
edited_by_id → Users > id

Notes recorded on RD Station CRM deals, with the text, who wrote it and when.

Field	Type
deal_id	text	[en] Identifier of the deal the note belongs to. Deals > > id
id	text	[en] Note identifier.
description	text	[en] Note text.
user_id	text	[en] Identifier of the user who wrote the note. Users > > id
registered_at	timestamp	[en] Timestamp when the note was recorded.
pinned_at	timestamp	[en] Timestamp when the note was pinned to the top of the deal.
edited_by_id	text	[en] Identifier of the user who last edited the note. Users > > id
edited_at	timestamp	[en] Timestamp of the last edit of the note.

Deals: products

Replication type: Incremental with update window or Full (user configurable)

Parameters:

Update window (days): How many days previous to the savepoint the records will still be replicated
Read start date (Savepoint): Initial date to replicate data

Relationships:

deal_id → Deals > id
product_id → Products > id

Products added to RD Station CRM deals, with price, quantity, discount and billing frequency of each line.

Field	Type
deal_id	text	[en] Identifier of the deal the product was added to. Deals > > id
id	text	[en] Identifier of the product line within the deal.
product_id	text	[en] Identifier of the product in the catalog. Products > > id
price	float	[en] Unit price applied in the deal.
quantity	float	[en] Quantity of the product in the deal.
discount_type	text	[en] Discount format: amount or percentage.
discount	float	[en] Discount applied, in the format indicated by discount_type.
total_price	float	[en] Total amount of the line, with quantity and discount already applied.
billing_frequency	text	[en] Billing frequency: one-time, monthly or annually.
created_at	timestamp	[en] Timestamp when the product line was created.
updated_at	timestamp	[en] Timestamp of the last update of the product line.

Lost reasons

This pipeline is free

Replication type: Full

Lost reasons registered in RD Station CRM. They explain why each deal marked as lost did not go through.

Field	Type
id	text	[en] Lost reason identifier.
name	text	[en] Lost reason name.
created_at	timestamp	[en] Timestamp when the lost reason was created.
updated_at	timestamp	[en] Timestamp of the last update of the lost reason.

Meetings

This pipeline is free

Replication type: Full

Relationships:

responsible_id → Users > id
organizer_id → Users > id
contact_ids → Contacts > id

Meetings scheduled in RD Station CRM, with time, duration, organizer and guests.

Field	Type
id	text	[en] Meeting identifier.
subject	text	[en] Meeting subject.
notes	text	[en] Notes registered in the meeting.
starts_at	timestamp	[en] Meeting start date and time.
ends_at	timestamp	[en] Meeting end date and time.
duration_minutes	int	[en] Meeting duration in minutes.
status	text	[en] Meeting status in RD Station CRM.
responsible_id	text	[en] Identifier of the user responsible for the meeting. Relates to the Users integration. Users > > id
organizer_id	text	[en] Identifier of the user who organized the meeting. Relates to the Users integration. Users > > id
contact_ids	text	[en] Identifiers of the contacts invited to the meeting, comma separated. They relate to the Contacts integration. Contacts > > id
created_at	timestamp	[en] Timestamp when the meeting was created.
updated_at	timestamp	[en] Timestamp of the last update of the meeting.

Products

This pipeline is free

Replication type: Full

RD Station CRM product catalog. The products actually sold in each deal are in the Deals: products integration.

Field	Type
id	text	[en] Product identifier.
name	text	[en] Product name.
description	text	[en] Product description.
price	float	[en] List price of the product.
visible	boolean	[en] Indicates whether the product is available to be added to deals.
custom_fields	text	[en] All of the product custom fields, as JSON. The following columns bring each custom field separately.
created_at	timestamp	[en] Timestamp when the product was created.
updated_at	timestamp	[en] Timestamp of the last update of the product.

Sales pipelines

This pipeline is free

Replication type: Full

Relationships:

stage_ids → Sales pipelines: stages > id

Sales pipelines registered in RD Station CRM. The stages of each pipeline are in the Sales pipelines: stages integration.

Field	Type
id	text	[en] Sales pipeline identifier.
name	text	[en] Sales pipeline name.
display_order	int	[en] Position of the pipeline in the RD Station CRM listing.
stage_ids	text	[en] Comma-separated identifiers of the pipeline stages, in order. Sales pipelines: stages > > id
created_at	timestamp	[en] Timestamp when the pipeline was created.
updated_at	timestamp	[en] Timestamp of the last update of the pipeline.

Sales pipelines: stages

This pipeline is free

Replication type: Full

Relationships:

pipeline_id → Sales pipelines > id

Stages of the RD Station CRM sales pipelines, in the order in which they appear in each pipeline.

Field	Type
pipeline_id	text	[en] Identifier of the sales pipeline the stage belongs to. Sales pipelines > > id
id	text	[en] Stage identifier.
name	text	[en] Stage name.
description	text	[en] Stage description.
objective	text	[en] Goal of the stage, that is, what needs to happen for the deal to move forward.
display_order	int	[en] Position of the stage within the pipeline.
created_at	timestamp	[en] Timestamp when the stage was created.
updated_at	timestamp	[en] Timestamp of the last update of the stage.

Segments

This pipeline is free

Replication type: Full

Segments (lines of business) registered in RD Station CRM and used to classify companies.

Field	Type
id	text	[en] Segment identifier.
name	text	[en] Segment name.
created_at	timestamp	[en] Timestamp when the segment was created.
updated_at	timestamp	[en] Timestamp of the last update of the segment.

Sources

This pipeline is free

Replication type: Full

Sources registered in RD Station CRM, that is, the channel through which each deal reached the company.

Field	Type
id	text	[en] Source identifier.
name	text	[en] Source name.
description	text	[en] Source description.
created_at	timestamp	[en] Timestamp when the source was created.
updated_at	timestamp	[en] Timestamp of the last update of the source.

Tasks

Replication type: Incremental or Full (user configurable)

Parameters:

Read start date (Savepoint): Initial date to replicate data

Relationships:

created_by_id → Users > id
completed_by_id → Users > id
deal_id → Deals > id
owner_ids → Users > id
user_id > _kdd_owners → Users > id

Main object

Tasks and activities recorded in RD Station CRM, with type, status, due date, owners and the related deal.

Field	Type
id	text	[en] Task identifier.
name	text	[en] Task title.
description	text	[en] Task description.
type	text	[en] Task type: call, email, meeting, task, lunch, visit or whatsapp.
status	text	[en] Task status: open, completed or canceled.
due_date	timestamp	[en] Task due date and time.
completed_at	timestamp	[en] Timestamp when the task was completed.
created_by_id	text	[en] Identifier of the user who created the task. Users > > id
completed_by_id	text	[en] Identifier of the user who completed the task. Users > > id
deal_id	text	[en] Identifier of the deal the task is linked to. Deals > > id
owner_ids	text	[en] Comma-separated identifiers of the users responsible for the task. Users > > id
owner_names	text	[en] Comma-separated names of the users responsible for the task, in the same order as the owner identifiers. Use it to DISPLAY the owner without joining the users table. Do not use it to GROUP: a task with more than one owner carries the whole list in a single cell, so grouping by this column yields one category per combination of owners instead of one per person -- to count or segment by owner use the task-user link table.
created_at	timestamp	[en] Timestamp when the task was created.
updated_at	timestamp	[en] Timestamp of the last update of the task.

rdstationcrm_v2_tasks_users

Link between RD Station CRM tasks and their owners: one row per owner of each task. Equivalent to the owner identifiers column of the tasks table, in a shape suitable for joining with the users table. This is the right shape to count or segment tasks BY owner; the owner names column of the tasks table is for display, not for grouping.

Field	Type
task_id	text	[en] Task identifier.
user_id	text	[en] Identifier of the user responsible for the task. Users > > id

Field

Type

task_id

text

[en] Task identifier.

user_id

text

[en] Identifier of the user responsible for the task.

Users > > id

Teams

This pipeline is free

Replication type: Full

Relationships:

user_ids → Users > id

Sales teams registered in RD Station CRM and the users belonging to each one.

Field	Type
team_id	text	[en] Team identifier.
name	text	[en] Team name.
user_ids	text	[en] Comma-separated identifiers of the users who belong to the team. Users > > id
created_at	timestamp	[en] Timestamp when the team was created.
updated_at	timestamp	[en] Timestamp of the last update of the team.

Users

This pipeline is free

Replication type: Full

Users of the RD Station CRM account. This table is how you find out who the owners of deals, companies and tasks are.

Field	Type
id	text	[en] User identifier.
name	text	[en] User name.
email	text	[en] User login e-mail.
phone	text	[en] User phone number.
created_at	timestamp	[en] Timestamp when the user was created.
updated_at	timestamp	[en] Timestamp of the last update of the user.

Notes

Important notes about RD Station CRM data:

Full (Integral) or Incremental: on Deals, Contacts, Companies, Tasks, Deals: products and Deals: notes you pick the mode when creating or editing the integration. In Incremental mode (default), each run reads only the records changed since the previous one. In Deals: products and Deals: notes, the deals changed in the last N days (the Update window) are re-read. Deletions only leave the table in Full (Integral) mode, which re-reads everything on every run.
Registries (pipelines, stages, users, teams, products, campaigns, sources, segments, lost reasons, custom fields) and Meetings are always Full.
Custom fields on Deals, Contacts, Companies and Products become one column each, named after the field. A field created in the CRM after the integration only shows up when the integration is edited or recreated. The Custom fields integration lists every field of the account; the slug column is the field key.
Names instead of ids: tables bring the pipeline, stage, owner, source, campaign and lost reason ids. To get the names, join with the registry integrations (Sales pipelines, Sales pipelines: stages, Users, etc.) by id.
Deal status comes as text: won, lost and ongoing. For lost deals, filter status = lost.
Lists come in a comma-separated column. A deal's contacts, a task's owners and a custom field's options also come in a table of their own, one row per item, for joining and counting. Each pipeline's stages are in the Sales pipelines: stages integration.
Dates and times are in the time zone RD Station CRM displays (Brasília time).
Texts arrive as they are in the CRM, with accents.
The on-screen position of pipelines, stages and fields is in the display_order column.
Stage history: the RD Station CRM API used by this data source does not provide the history of deal movements between stages, only the current stage. That is why it does not have the Stage history integration of the RD Station CRM (legacy) data source.

Part of this documentation was automatically generated by AI and may contain errors. We recommend verifying critical information

Written by

Thassyo Pereira·Published 2026-10-28·Updated 2026-11-03