Source connector
RD Station CRM connector
RD Station CRM integration for databases, warehouses and BI tools
Sales CRM paired with RD Station inbound marketing. Datrise captures RD Station CRM entities such as deals, contacts, organizations, funnel stages, activities and loss reasons, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.
The RD Station CRM API v1 (crm.rdstation.com/api/v1) and API v2 (api.rd.services/crm/v2) authenticates with personal access token, OAuth 2.0, incremental runs key on updated_at, and RD Station CRM caps calls at 120 requests per minute across GET, POST, PUT and DELETE on Basic, Pro and Advanced plans; v2 answers 429 Too Many Requests with a `Retry-After` header in seconds.
Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `rd_station_crm_deals`) with a schema derived from the RD Station CRM API rather than a flattened CSV, in any of the 43 supported destinations.
Datrise is in early access: pick a destination below to open the RD Station CRM pipeline page, and join the waitlist to get the RD Station CRM connector (CRM) with guided onboarding.
What RD Station CRM data Datrise extracts
Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.
| Object | Landing table | Sync mode |
|---|---|---|
| deals | rd_station_crm_deals | Upsert by primary key, incremental on updated-at |
| contacts | rd_station_crm_contacts | Upsert by primary key, incremental on updated-at |
| organizations | rd_station_crm_organizations | Upsert by primary key, incremental on updated-at |
| funnel stages | rd_station_crm_funnel_stages | Upsert by primary key, incremental on updated-at |
| activities | rd_station_crm_activities | Append-only, incremental by timestamp |
| loss reasons | rd_station_crm_loss_reasons | Upsert by primary key, incremental on updated-at |
RD Station CRM API: setup facts for the connector
Verified against the vendor documentation on 2026-10-05. Unknown values are left blank rather than guessed.
| API | RD Station CRM API v1 (crm.rdstation.com/api/v1) and API v2 (api.rd.services/crm/v2) |
|---|---|
| Authentication | personal access token, OAuth 2.0 — API v1 authenticates with a per-user token that is unique and immutable per RD Station CRM user and is sent as the `token` query-string parameter on every request; API v2 uses OAuth 2.0 authorization code via an app registered in the RD Station App Store, with `access_token` valid for 2 hours (7200 seconds) sent as a Bearer header and a rolling `refresh_token` that expires after 14 days without use. |
| Pagination | page — v1 list endpoints take `page` and `limit` (default 20, maximum 200) and return `total`, `has_more` and a `next_page` value; v2 uses `page[number]` and `page[size]` with `links.first/prev/next/last` in the response; on both versions the list endpoints for deals, organizations and contacts return only the first 10,000 records of a query. |
| Rate limit | 120 requests per minute across GET, POST, PUT and DELETE on Basic, Pro and Advanced plans; v2 answers 429 Too Many Requests with a `Retry-After` header in seconds |
| Incremental cursor | updated_at — Only API v2 exposes it: `filter=updated_at:>="2023-01-01 12:00:00"` (RDQL, DateTime values quoted) on `/deals`, `/contacts`, `/organizations` and `/tasks`; v1 `/deals` only filters on `created_at_period` or `closed_at_period` with `start_date`/`end_date`, and v1 `/contacts` and `/organizations` have no date filter at all. |
| Webhooks | Yes — Webhooks (`POST /api/v1/webhooks` with `event_type`, e.g. crm_deal_created / crm_deal_updated / crm_deal_deleted, plus contact, organization, task, product, campaign, source and lost-reason events) |
| Bulk export | No |
| Deletes detectable | Yes — Only through webhooks: `crm_deal_deleted`, `crm_contact_deleted` and `crm_organization_deleted` events carry the deleted record in `document`; neither API version documents a deleted flag or a deleted-records listing. |
What bites when replicating RD Station CRM
- The v1 `token` is a per-user secret passed in the query string (OpenAPI security scheme `apiKey` in `query`), so it lands in proxy and server access logs, and every list result is scoped by that user's visibility level (Restrito, Equipe or Geral): a Restrito user's token lists only the deals, organizations and contacts they own.
- The list endpoints for deals, organizations and contacts return at most the first 10,000 records of any query on both v1 and v2, so a backfill of a larger account has to be partitioned by `created_at` or `updated_at` windows; exporting more than 10,000 deals in one go exists only as a CSV download in the UI on Basic and Pro plans.
- API v1 has no updated-at filter: `/deals` accepts only `created_at_period` or `closed_at_period` with `start_date`/`end_date` (format `2020-12-14T15:00:00`), and `/contacts` and `/organizations` take no date filter, so incremental sync requires the v2 RDQL `updated_at:>=` filter, whose DateTime literals must be quoted (`"2023-01-01 12:00:00"`).
- Webhook deliveries are retried only 5 more times, and a callback that takes longer than 5 seconds to respond or returns a non-2xx status counts as a failed delivery; the JSON payload is fixed and cannot be customised, and `http_method` supports POST only.
Popular destinations for RD Station CRM
Choose a destination below to open the ready pipeline page.
- AAirtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline - AAmazon Athena
Serverless SQL over S3 data lake tables.
View pipeline - AAmazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline - AAmazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline - AAmazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline - AAmazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline - AApache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline - AAzure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline - AAzure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline
RD Station CRM connector FAQ
- What RD Station CRM data does the connector extract?
- 6 objects: deals, contacts, organizations, funnel stages, activities and loss reasons. Each lands in its own table with types preserved; history-style objects (1: activities) load as append-only streams.
- Is the RD Station CRM integration incremental?
- Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
- Where can I load RD Station CRM data?
- Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each RD Station CRM → destination pair has its own page with the object-to-table mapping.
Related CRM sources
Other sources in the same category, each with its own connector page.
Early access
Launch your RD Station CRM pipeline with guided onboarding
Join the waitlist to get priority access for RD Station CRM integrations with guided setup, schema-aware mapping, and production-grade incremental sync.