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 credentials for authentication. The connector supports both the legacy v1 API and the new v2 OAuth2 API. The following configurations are available:

API Version: API version to use. Use v2 for the most recent API and v1 for the legacy one.
Access Token: (v1 only) The token required to authenticate against the v1 API service. Check the RD Station CRM docs to discover how you can generate your access token.
OAuth2 Authorization: (v2 only) Authorize with your user account and grant permissions for the Nekt app.
Start Date: The earliest record date to sync (ISO 8601 format, e.g. 2024-01-01T00:00:00Z). Used for incremental streams.
Activities API Token (optional, advanced settings): A legacy v1 API token that enables the whatsapp_transcriptions stream (WhatsApp conversation transcripts from the deal timeline). This endpoint has no v2 equivalent, so it requires its own token regardless of the API version selected. Note: This feature requires the Advanced plan of RD Station CRM. If you provide a token but your account does not have access, the stream will be automatically skipped. Leave it empty and the stream is not created.

Once you’re done, click Next.

2. Select streams

If you are using the v1 API, incremental syncs are not supported. 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 for v1. The v2 API supports incremental syncs for Contacts, Deals, Organizations and Deal Notes; the remaining v2 streams are full table. The Tasks endpoint cannot be filtered by update date, so it is always a full table sync — but in v2 the connector pages past the 10,000-record query limit using a due_date cursor, so every task is fetched (see the Tasks stream below).

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

Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description. The available streams depend on the API version setting: v1 (legacy access-token API) exposes one set of streams, while v2 (OAuth2 API, the default for new sources) exposes another. The opt-in whatsapp_transcriptions stream is available with either version when an Activities API Token is provided. Version 1 (v1, default):

Stream	Slug	Description
Companies	`companies`	Organizations (companies) registered in the CRM.
Contacts	`contacts`	Contacts registered in the CRM.
Custom Fields	`custom_fields`	Definitions of the account’s custom fields.
Deal Pipelines	`deal_pipelines`	Sales pipelines configured in the CRM.
Deal Stages	`deal_stages`	Stages that make up each deal pipeline.
Deals	`deals`	Deals (opportunities) and their attributes.
Deals Details	`deals_details`	Full detail of each deal, fetched per deal id.
Products	`products`	Products available in the CRM.
Reasons for Loss	`reasons_for_loss`	Registered reasons for losing a deal.
Tasks	`tasks`	Tasks and activities linked to deals and contacts.
Users	`users`	Users of the CRM account.
WhatsApp Transcriptions	`whatsapp_transcriptions`	(opt-in) WhatsApp conversation transcripts logged on the deal timeline. Requires the Activities API Token and the Advanced plan.

Version 2 (v2, OAuth2 API):

Stream	Slug	Description
Contacts	`contacts`	Contacts registered in the CRM.
Deals	`deals`	Deals (opportunities) and their attributes.
Deal Notes	`deal_notes`	Notes attached to each deal, fetched per deal id.
Deal Products	`deal_products`	Products associated with each deal, fetched per deal id.
Organizations	`organizations`	Organizations (companies) registered in the CRM.
Users	`users`	Users of the CRM account.
Teams	`teams`	Teams configured in the account.
Tasks	`tasks`	Tasks and activities linked to deals and contacts.
Products	`products`	Products available in the CRM.
Pipelines	`pipelines`	Sales pipelines configured in the CRM.
Stages	`stages`	Stages that make up each pipeline, fetched per pipeline id.
Custom Fields	`custom_fields`	Definitions of the account’s custom fields.
Campaigns	`campaigns`	Marketing campaigns registered in the CRM.
Sources	`sources`	Deal sources configured in the account.
Lost Reasons	`lost_reasons`	Registered reasons for losing a deal.
Segments	`segments`	Organization segments configured in the account.
WhatsApp Transcriptions	`whatsapp_transcriptions`	(opt-in) WhatsApp conversation transcripts logged on the deal timeline. Requires the Activities API Token and the Advanced plan.

Fields by stream

Below you’ll find all available data streams from RD Station CRM and their corresponding fields:

Campaigns

Stream containing marketing campaign records. Available in the v2 API.

Companies

Stream containing organization (company) records from your CRM. Available in the v1 API.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the company
`name`	String	Name of the company
`resume`	String	Short description of the company
`url`	String	Website URL of the company
`address`	String	Address of the company
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated
`won_count`	Number	Number of won deals
`lost_count`	Number	Number of lost deals
`opened_count`	Number	Number of open deals
`paused_count`	Number	Number of paused deals
`organization_segments`	Array	Array of segments the company belongs to, each with `id`, `name`, `integration_id`, and timestamps
`user`	Object	Assigned user with `id`, `name`, `nickname`, and `email`
`contacts`	Array	Array of contact people with `name`, `title`, `notes`, `emails`, `phones`, `birthday`, and social profiles (`facebook`, `linkedin`, `skype`)
`custom_fields`	String	Custom fields for the entity, serialized as a JSON string (object keyed by RD Station field slug; v2 API)

Contacts

Stream containing individual contact records from your CRM. Supported by both v1 and v2 APIs.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the contact
`name`	String	Name of the contact
`title`	String	Job title of the contact
`notes`	String	Notes about the contact
`organization_id`	String	Identifier of the associated company
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated
`emails`	Array	Array of email objects with `email` and timestamps
`phones`	Array	Array of phone objects with `phone`, `type`, `whatsapp`, `whatsapp_full_internacional`, `whatsapp_url_web`, and timestamps
`birthday`	Object	Object with `day`, `month`, `year`, and timestamps
`facebook`	String	Facebook profile
`linkedin`	String	LinkedIn profile
`skype`	String	Skype handle
`contact_custom_fields`	Array	Array of custom field values with `custom_field_id`, `value`, and timestamps (v1 API)
`custom_fields`	String	Custom fields for the entity, serialized as a JSON string (object keyed by RD Station field slug; v2 API)
`legal_bases`	Array	Array of legal bases with `category`, `type`, and `status`
`deals`	Array	Array of associated deals with `id`, `name`, `prediction_date`, `win`, `deal_lost_reason_id`, and `closed_at`

Custom Fields

Stream containing custom field definitions configured in your CRM. These define the structure for custom data on deals, contacts, companies, and products. Supported by both v1 and v2 APIs.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the custom field
`label`	String	Display label of the custom field
`type`	String	Field type (e.g., text, number, select)
`for`	String	Entity the field applies to (e.g., deal, contact, organization)
`order`	Number	Display order of the field
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated
`required`	Boolean	Whether the field is required
`unique`	Boolean	Whether the field must be unique
`visible`	Boolean	Whether the field is visible in the UI
`allow_new`	Boolean	Whether new values can be added (for select-type fields)
`opts`	Array	Array of available options for select-type fields
`required_rules`	Array	Array of conditional rules defining when the field is required, each with `property` and `value`

Deal Notes

Stream containing textual notes added to deals. Available in the v2 API.

Deal Pipelines

Stream containing sales pipeline definitions. Each pipeline organizes deals into sequential stages. Available in the v1 API.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the pipeline
`name`	String	Name of the pipeline
`order`	Number	Display order of the pipeline
`deal_stages`	Array	Array of stages within the pipeline, each with `id`, `name`, `nickname`, `order`, `objective`, and `description`

Deal Products

Stream containing products attached to individual deals. This is a child stream of Deals, fetched per deal id. It is a join-table resource (per-deal pricing and quantity): to enrich it with product details, join with the Products stream on product_id downstream. This stream is a full table sync. Available in the v2 API.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the deal-product association
`deal_id`	String	ID of the associated deal (injected from the parent Deals stream)
`product_id`	String	ID of the product
`price`	Number	Negotiated unit price for this deal
`quantity`	Number	Quantity of the product in the deal
`discount`	Number	Discount applied
`discount_type`	String	Discount type (`amount` or `percentage`)
`total_price`	Number	Total price after discount
`billing_frequency`	String	Billing frequency (`one-time`, `monthly`, `annually`)
`created_at`	Timestamp	Timestamp when the association was created
`updated_at`	Timestamp	Timestamp when the association was last updated

Deal Stages

Stream containing deal stage records for each pipeline. This is a child stream of Deal Pipelines, fetching stages per pipeline with full detail. Available in the v1 API.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the stage
`name`	String	Name of the stage
`nickname`	String	Short nickname of the stage
`order`	Number	Position of the stage within the pipeline
`objective`	String	Objective or goal of this stage
`description`	String	Detailed description of the stage
`instance_id`	String	Identifier of the associated instance
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated
`deal_pipeline`	Object	Parent pipeline with `id`, `name`, and `order`

Deals

Stream containing deal (opportunity) records. This is the core sales entity in RD Station CRM. Supported by both v1 and v2 APIs.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the deal
`name`	String	Name of the deal
`rating`	Number	Deal rating
`win`	Boolean	Whether the deal was won
`hold`	Boolean	Whether the deal is on hold
`interactions`	Number	Number of interactions on the deal
`prediction_date`	Date	Expected closing date
`closed_at`	Timestamp	Timestamp when the deal was closed
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated
`amount_montly`	Number	Monthly recurring amount
`amount_total`	Number	Total deal amount
`amount_unique`	Number	One-time amount
`last_activity_at`	Timestamp	Timestamp of the last activity
`last_activity_content`	String	Content of the last activity
`user_changed`	Boolean	Whether the assigned user was changed
`markup`	String	Markup content
`markup_created`	String	Markup creation info
`markup_last_activities`	String	Markup of last activities
`deal_stage`	Object	Current stage with `id`, `name`, and `nickname`
`deal_source`	Object	Source of the deal with `id` and `name`
`deal_lost_reason`	Object	Reason for loss with `id` and `name`
`user`	Object	Assigned user with `id`, `name`, `nickname`, and `email`
`organization`	Object	Associated company with `id`, `name`, `address`, coordinates, and nested `user`
`contacts`	Array	Array of associated contacts with names, emails, phones, birthday, and social profiles
`deal_custom_fields`	Array	Array of custom field values with the full custom field definition (v1 API)
`custom_fields`	String	Custom fields for the entity, serialized as a JSON string (object keyed by RD Station field slug; v2 API)
`deal_products`	Array	Array of products attached to the deal with `name`, `base_price`, `price`, `amount`, `discount`, `discount_type`, `recurrence`, and `total`
`campaign`	Object	Associated campaign with `id` and `name`
`next_task`	Object	Next scheduled task with `id`, `date`, `subject`, `type`, and `hour`

Deals Details

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. Available in the v1 API.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the deal
`name`	String	Name of the deal
`rating`	Number	Deal rating
`win`	Boolean	Whether the deal was won
`hold`	Boolean	Whether the deal is on hold
`interactions`	Number	Number of interactions
`prediction_date`	Date	Expected closing date
`closed_at`	Timestamp	Timestamp when the deal was closed
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated
`amount_montly`	Number	Monthly recurring amount
`amount_total`	Number	Total deal amount
`amount_unique`	Number	One-time amount
`best_moment_to_touch`	Boolean	Whether it’s the best moment to contact
`deal_lost_note`	String	Note explaining why the deal was lost
`deal_source_id`	String	Identifier of the deal source
`deal_lost_reason_id`	String	Identifier of the deal lost reason
`campaign_id`	String	Identifier of the associated campaign
`from_rdsm_integration`	Boolean	Whether the deal came from RD Station Marketing
`last_note_content`	String	Content of the last note
`deal_stage`	Object	Current stage with `id`, `name`, `nickname`, and `deal_pipeline_id`
`deal_pipeline`	Object	Associated pipeline with `id` and `name`
`deal_source`	Object	Source of the deal with `id`, `name`, and `deal_source_id`
`campaign`	Object	Associated campaign with `id`, `name`, and `campaign_id`
`user`	Object	Assigned user with `id` and `name`
`organization`	Object	Associated company with full detail including `organization_custom_fields` and `organization_segments`
`deal_custom_fields`	Array	Array of custom field values with the full custom field definition (v1 API)
`custom_fields`	String	Custom fields for the entity, serialized as a JSON string (object keyed by RD Station field slug; v2 API)
`deal_products`	Array	Array of products with `name`, `base_price`, `price`, `amount`, `discount`, `discount_type`, `recurrence`, and `total`
`deal_stage_histories`	Array	Array of stage transitions with `deal_stage_id`, `start_date`, and `end_date`
`stop_time_limit`	Object	Stagnation info with `expiration_date_time`, `expired`, and `expired_days`
`deal_pipeline_relation`	Object	Pipeline relation with `parent_deal` containing deal summary, pipeline, stage, and user info

Lost Reasons

Stream containing deal loss reason definitions configured in your CRM. Available in the v2 API.

Organizations

Stream containing organization (company) records from your CRM. Available in the v2 API.

Pipelines

Stream containing sales pipeline definitions. Available in the v2 API.

Products

Stream containing product records from your CRM catalog. Supported by both v1 and v2 APIs.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the product
`name`	String	Name of the product
`description`	String	Description of the product
`base_price`	Number	Base price of the product
`visible`	Boolean	Whether the product is visible
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated
`product_custom_fields`	Array	Array of custom field values with `custom_field_id`, `value`, and timestamps

Reasons for Loss

Stream containing deal loss reason definitions configured in your CRM. Available in the v1 API.Key Fields:

Field	Type	Description
`_id`	String	Unique identifier of the reason
`name`	String	Name of the loss reason
`instance_id`	String	Identifier of the associated instance
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated

Segments

Stream containing organization segment definitions. Available in the v2 API.

Sources

Stream containing deal source definitions. Available in the v2 API.

Stages

Stream containing deal stage definitions. Available in the v2 API.

Tasks

Stream containing task records associated with deals. Supported by both v1 and v2 APIs.

The RD Station Tasks endpoint cannot be filtered by creation or update date, so incremental syncs are not possible and this stream is forced to FULL_TABLE sync in both API versions. In v1 the extraction is capped at the most recent 10,000 records. In v2 the connector sorts tasks by due_date ascending and, whenever a query hits RD Station’s 10,000-record limit, re-issues it from the last due_date seen, so accounts with more than 10,000 tasks are fully extracted (the sync just takes a few more passes). Rows re-read at the cursor boundary or shifted by page drift are deduplicated by id within the run.

Key Fields (v1 API):

Field	Type	Description
`id`	String	Unique identifier of the task
`subject`	String	Subject of the task
`type`	String	Type of the task (e.g., call, email, meeting)
`status`	String	Current status of the task
`done`	Boolean	Whether the task is completed
`done_date`	Timestamp	Timestamp when the task was completed
`date`	Date	Scheduled date of the task
`hour`	String	Scheduled hour of the task
`notes`	String	Notes about the task
`markup`	String	Markup content
`deal_id`	String	Identifier of the associated deal
`user_ids`	Array	Array of assigned user identifiers
`created_at`	Timestamp	Timestamp when the record was created
`deal`	Object	Associated deal summary with `id`, `name`, `hold`, and `rating`
`users`	Array	Array of assigned users with `id`, `name`, `nickname`, and `email`

Key Fields (v2 API):

Field	Type	Description
`id`	String	Unique identifier of the task
`name`	String	Name/title of the task
`description`	String	Description of the task
`type`	String	Task type (e.g., call, email, meeting)
`status`	String	Status (open, completed, canceled)
`due_date`	Timestamp	Scheduled due date for the task
`completed_at`	Timestamp	Timestamp when the task was completed
`created_by_id`	String	ID of the user who created the task
`completed_by_id`	String	ID of the user who completed the task
`deal_id`	String	ID of the associated deal
`owner_ids`	Array	IDs of users assigned to the task
`created_at`	Timestamp	Timestamp when the task was created
`updated_at`	Timestamp	Timestamp when the task was last updated

Teams

Stream containing CRM team records. Available in the v2 API.

Users

Stream containing CRM user (team member) records. Supported by both v1 and v2 APIs.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the user
`name`	String	Name of the user
`email`	String	Email of the user
`active`	Boolean	Whether the user is active
`hidden`	Boolean	Whether the user is hidden
`last_login`	Timestamp	Timestamp of the user’s last login
`created_at`	Timestamp	Timestamp when the record was created
`updated_at`	Timestamp	Timestamp when the record was last updated

WhatsApp Transcriptions

Opt-in stream containing WhatsApp conversation transcripts logged on the deal timeline. It is backed by the legacy v1 /activities endpoint (filtered to whatsapp_transcription activities), which has no v2 equivalent, so it always authenticates with the dedicated Activities API Token and is only created when that token is configured.

Advanced Plan Required: WhatsApp transcripts require the Advanced plan of RD Station CRM. If the Activities API Token is configured but the account is not on the Advanced plan, the connector will detect the lack of permissions and automatically skip this stream (it will not be created or updated).

Supports incremental syncs on date, starting from the configured Start Date.Key Fields:

Field	Type	Description
`id`	String	Unique identifier of the activity record
`_id`	String	Internal unique identifier of the activity record
`deal_id`	String	ID of the deal this WhatsApp transcript is logged against
`user_id`	String	ID of the CRM user associated with the conversation
`text`	String	Full WhatsApp conversation transcript, as recorded on the deal timeline
`date`	Timestamp	Timestamp when the transcript activity was registered

Transformation example: pivoting custom fields to columns

The custom_fields column stores all account-specific custom attributes as a single JSON string. This ensures schema stability regardless of dynamically created fields in RD Station and prevents extraction issues. To analyze dimensions like document numbers, values, or dropdown options in Explorer or downstream models, parse the JSON and expose the keys as separate columns.

SQL transformation (AWS Athena / GCP BigQuery)

AWS (Athena)
GCP (BigQuery)

SELECT
   id,
   created_at,
   updated_at,
   json_extract_scalar(custom_fields, '$.segmento') AS segmento,
   CAST(json_extract_scalar(custom_fields, '$.valor') AS DOUBLE) AS valor
FROM
   nekt_raw.rd_station_crm_contacts

Note: If your RD Station slug contains hyphens (e.g., cpf-cliente), you may need to use bracket notation in your JSON path extraction depending on your SQL engine syntax, such as json_extract_scalar(custom_fields, '$["cpf-cliente"]').

SELECT
   id,
   created_at,
   updated_at,
   JSON_VALUE(custom_fields, '$.segmento') AS segmento,
   SAFE_CAST(JSON_VALUE(custom_fields, '$.valor') AS FLOAT64) AS valor
FROM
   `nekt_raw.rd_station_crm_contacts`

Note: If your RD Station slug contains hyphens (e.g., cpf-cliente), you may need to use quoted identifiers in your JSON path extraction, such as JSON_VALUE(custom_fields, '$."cpf-cliente"').

Implementation Notes

Incremental syncs and the 10,000-record query limit (v2)

RD Station’s v2 API rejects any filtered listing past the 10,000th record. For the incremental streams (Contacts, Deals, Organizations, Deal Notes) the connector filters on the replication key from the last saved state (or the Start Date) and, when a window overflows the limit, advances a monotonic cursor (created_at ascending) or splits the window until every slice fits, so no records are lost on the first sync of a large account.
Deal Products and Deal Notes are child streams fetched once per deal returned by the Deals stream. Deal Products has no replication key of its own and is always a full table sync.

Tasks pagination and page drift

The Tasks endpoint does not guarantee a stable order between calls unless explicitly sorted, so records changing mid-extraction can shift pages (page drift), producing duplicate or skipped rows.
In v2 the connector always sorts Tasks by due_date ascending. A task inserted before the current page can only shift later pages forward, so drift can duplicate a row but never skip one; duplicates are removed by id within the run.
due_date is also the one field that is both filterable and sortable and mandatory on every task, so it doubles as the cursor that pages past the 10,000-record limit: when a pass hits the cap, the query is re-issued with due_date >= <last due_date seen> until a pass finishes without overflowing. If the cursor cannot advance (more than 10,000 tasks sharing the same due_date), the run finishes with a partial result and a warning in the logs.

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.

Troubleshooting

Error or symptom	What it means	What to do
A custom field column is missing from the table	Custom fields arrive consolidated in a single JSON column, not as separate columns.	Read the field from the JSON column. See Transformation example: pivoting custom fields to columns.
`429 Too Many Requests`	You hit RD Station’s rate limit.	Reduce concurrency by scheduling sources that share the account at different times.
The `whatsapp_transcriptions` stream returns no data	This stream requires an Advanced plan on RD Station and an Activities API Token filled in the source settings.	Confirm the plan with RD Station and fill in the Activities API Token.
Extraction only brings the last 30 days even though an initial sync date is set	The API only honors the date filter when a start and an end date are sent together.	Set both dates on the stream.

Incremental streams are also bounded by RD Station’s 10,000-record query limit, and Tasks pagination has its own behavior. Both are described in Implementation Notes.

Skills for agents

Download RD Station CRM skills file

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

Documentation

Get started

Context

Activate

Workspace

Resources

RD Station CRM as a data source

Configuring RD Station CRM as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Available streams

Fields by stream

Transformation example: pivoting custom fields to columns

Implementation Notes

Incremental syncs and the 10,000-record query limit (v2)

Data Model

Troubleshooting

Skills for agents

Download RD Station CRM skills file

​Configuring RD Station CRM as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

​Available streams

​Fields by stream

​Transformation example: pivoting custom fields to columns

​Implementation Notes

​Incremental syncs and the 10,000-record query limit (v2)

​Tasks pagination and page drift

​Data Model

​Troubleshooting

​Skills for agents

Download RD Station CRM skills file

Configuring RD Station CRM as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Available streams

Fields by stream

Transformation example: pivoting custom fields to columns

Implementation Notes

Incremental syncs and the 10,000-record query limit (v2)

Tasks pagination and page drift

Data Model

Troubleshooting

Skills for agents