Skip to main content
RD Station CRM is a customer relationship management platform that helps businesses manage leads, opportunities, and customer interactions. It provides tools for contact management, deal tracking, sales pipeline management, and customer analytics to improve sales performance and customer relationships.

​
Configuring RD Station CRM as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the RD Station CRM option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide your RD Station CRM access token for authentication. The following configuration is available:
  • Access Token: The token required to authenticate against the API service. Check the RD Station CRM docs to discover how you can generate your access token. This token provides access to your RD Station CRM data including contacts, deals, companies, and other entities.
Once you’re done, click Next.

​
2. Select streams

The RD Station CRM API doesn’t support incremental syncs. It also has a limitation of a maximum of 10,000 records per endpoint. Thus, this connector will always fetch the most recent 10,000 records for each entity (e.g. Deals, Contacts, Companies, etc) in each run.
Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: depending on the data you are bringing to the lake, you can choose between INCREMENTAL and FULL_TABLE. Read more about Sync Types here.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from RD Station CRM and their corresponding fields:
Stream containing organization (company) records from your CRM.Key Fields:
  • id - Unique identifier of the company
  • name - Name of the company
  • resume - Short description of the company
  • url - Website URL of the company
  • address - Address of the company
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated
Deal Counts:
  • won_count - Number of won deals
  • lost_count - Number of lost deals
  • opened_count - Number of open deals
  • paused_count - Number of paused deals
Nested Objects:
  • organization_segments - Array of segments the company belongs to, each with id, name, integration_id, and timestamps
  • user - Assigned user with id, name, nickname, and email
  • contacts - Array of contact people with name, title, notes, emails, phones, birthday, and social profiles (facebook, linkedin, skype)
  • custom_fields - Array of custom field values with custom_field_id, value, and the full custom field definition
Stream containing individual contact records from your CRM.Key Fields:
  • id - Unique identifier of the contact
  • name - Name of the contact
  • title - Job title of the contact
  • notes - Notes about the contact
  • organization_id - Identifier of the associated company
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated
Contact Information:
  • emails - Array of email objects with email and timestamps
  • phones - Array of phone objects with phone, type, whatsapp, whatsapp_full_internacional, whatsapp_url_web, and timestamps
  • birthday - Object with day, month, year, and timestamps
Social Profiles:
  • facebook - Facebook profile
  • linkedin - LinkedIn profile
  • skype - Skype handle
Nested Objects:
  • contact_custom_fields - Array of custom field values with custom_field_id, value, and timestamps
  • legal_bases - Array of legal bases with category, type, and status
  • deals - Array of associated deals with id, name, prediction_date, win, deal_lost_reason_id, and closed_at
Stream containing custom field definitions configured in your CRM. These define the structure for custom data on deals, contacts, companies, and products.Key Fields:
  • id - Unique identifier of the custom field
  • label - Display label of the custom field
  • type - Field type (e.g., text, number, select)
  • for - Entity the field applies to (e.g., deal, contact, organization)
  • order - Display order of the field
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated
Configuration:
  • required - Whether the field is required
  • unique - Whether the field must be unique
  • visible - Whether the field is visible in the UI
  • allow_new - Whether new values can be added (for select-type fields)
  • opts - Array of available options for select-type fields
  • required_rules - Array of conditional rules defining when the field is required, each with property and value
Stream containing sales pipeline definitions. Each pipeline organizes deals into sequential stages.Key Fields:
  • id - Unique identifier of the pipeline
  • name - Name of the pipeline
  • order - Display order of the pipeline
Nested Objects:
  • deal_stages - Array of stages within the pipeline, each with id, name, nickname, order, objective, and description
Stream containing deal stage records for each pipeline. This is a child stream of Deal Pipelines, fetching stages per pipeline with full detail.Key Fields:
  • id - Unique identifier of the stage
  • name - Name of the stage
  • nickname - Short nickname of the stage
  • order - Position of the stage within the pipeline
  • objective - Objective or goal of this stage
  • description - Detailed description of the stage
  • instance_id - Identifier of the associated instance
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated
Nested Objects:
  • deal_pipeline - Parent pipeline with id, name, and order
Stream containing deal (opportunity) records. This is the core sales entity in RD Station CRM.Key Fields:
  • id - Unique identifier of the deal
  • name - Name of the deal
  • rating - Deal rating
  • win - Whether the deal was won
  • hold - Whether the deal is on hold
  • interactions - Number of interactions on the deal
  • prediction_date - Expected closing date
  • closed_at - Timestamp when the deal was closed
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated
Monetary Values:
  • amount_montly - Monthly recurring amount
  • amount_total - Total deal amount
  • amount_unique - One-time amount
Activity:
  • last_activity_at - Timestamp of the last activity
  • last_activity_content - Content of the last activity
  • user_changed - Whether the assigned user was changed
  • markup - Markup content
  • markup_created - Markup creation info
  • markup_last_activities - Markup of last activities
Nested Objects:
  • deal_stage - Current stage with id, name, and nickname
  • deal_source - Source of the deal with id and name
  • deal_lost_reason - Reason for loss with id and name
  • user - Assigned user with id, name, nickname, and email
  • organization - Associated company with id, name, address, coordinates, and nested user
  • contacts - Array of associated contacts with names, emails, phones, birthday, and social profiles
  • deal_custom_fields - Array of custom field values with the full custom field definition
  • deal_products - Array of products attached to the deal with name, base_price, price, amount, discount, discount_type, recurrence, and total
  • campaign - Associated campaign with id and name
  • next_task - Next scheduled task with id, date, subject, type, and hour
Stream containing extended deal information. This is a child stream of Deals that fetches the full detail endpoint for each deal, including stage history and pipeline relations not available in the Deals list.Key Fields:
  • id - Unique identifier of the deal
  • name - Name of the deal
  • rating - Deal rating
  • win - Whether the deal was won
  • hold - Whether the deal is on hold
  • interactions - Number of interactions
  • prediction_date - Expected closing date
  • closed_at - Timestamp when the deal was closed
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated
Monetary Values:
  • amount_montly - Monthly recurring amount
  • amount_total - Total deal amount
  • amount_unique - One-time amount
Additional Detail Fields:
  • best_moment_to_touch - Whether it’s the best moment to contact
  • deal_lost_note - Note explaining why the deal was lost
  • deal_source_id - Identifier of the deal source
  • deal_lost_reason_id - Identifier of the deal lost reason
  • campaign_id - Identifier of the associated campaign
  • from_rdsm_integration - Whether the deal came from RD Station Marketing
  • last_note_content - Content of the last note
Nested Objects:
  • deal_stage - Current stage with id, name, nickname, and deal_pipeline_id
  • deal_pipeline - Associated pipeline with id and name
  • deal_source - Source of the deal with id, name, and deal_source_id
  • campaign - Associated campaign with id, name, and campaign_id
  • user - Assigned user with id and name
  • organization - Associated company with full detail including organization_custom_fields and organization_segments
  • deal_custom_fields - Array of custom field values with the full custom field definition (including display_rules, required_rules, slug, input_format, input_mask)
  • deal_products - Array of products with name, base_price, price, amount, discount, discount_type, recurrence, and total
  • deal_stage_histories - Array of stage transitions with deal_stage_id, start_date, and end_date
  • stop_time_limit - Stagnation info with expiration_date_time, expired, and expired_days
  • deal_pipeline_relation - Pipeline relation with parent_deal containing deal summary, pipeline, stage, and user info
Stream containing product records from your CRM catalog.Key Fields:
  • id - Unique identifier of the product
  • name - Name of the product
  • description - Description of the product
  • base_price - Base price of the product
  • visible - Whether the product is visible
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated
Nested Objects:
  • product_custom_fields - Array of custom field values with custom_field_id, value, and timestamps
Stream containing deal loss reason definitions configured in your CRM.Key Fields:
  • _id - Unique identifier of the reason
  • name - Name of the loss reason
  • instance_id - Identifier of the associated instance
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated
Stream containing task records associated with deals.Key Fields:
  • id - Unique identifier of the task
  • subject - Subject of the task
  • type - Type of the task (e.g., call, email, meeting)
  • status - Current status of the task
  • done - Whether the task is completed
  • done_date - Timestamp when the task was completed
  • date - Scheduled date of the task
  • hour - Scheduled hour of the task
  • notes - Notes about the task
  • markup - Markup content
  • deal_id - Identifier of the associated deal
  • user_ids - Array of assigned user identifiers
  • created_at - Timestamp when the record was created
Nested Objects:
  • deal - Associated deal summary with id, name, hold, and rating
  • users - Array of assigned users with id, name, nickname, and email
Stream containing CRM user (team member) records.Key Fields:
  • id - Unique identifier of the user
  • name - Name of the user
  • email - Email of the user
  • active - Whether the user is active
  • hidden - Whether the user is hidden
  • last_login - Timestamp of the user’s last login
  • created_at - Timestamp when the record was created
  • updated_at - Timestamp when the record was last updated

​
Data Model

The following diagram illustrates the relationships between the core data streams in RD Station CRM. The arrows indicate the join keys that link the different entities.

​
Skills for agents

Download RD Station CRM skills file

RD Station CRM connector documentation as plain markdown, for use in AI agent contexts.