Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

RD Station Marketing — connector

Reads segmentations, contacts of a segmentation, and conversions per asset from the RD Station Marketing API and loads them into the Bronze layer.

On this page (15)

Leia antes: ../conectores.md (state map) e fichas.md (index of datasheets).


What it does#

Reads segmentations, contacts of a segmentation, and conversions per asset from the RD Station Marketing API and loads them into the Bronze layer.

Supported ingestion modes:

  • We fetch — We fetch the data from your source.

Purpose#

Bring RD Station Marketing data into your datalake and make it available to the Bronze/Silver/Gold layers, BI models, and the natural language question wizard.

When to use / when not to use#

Use when you need to consolidate this source in the datalake on a scheduled basis, with isolation per workspace.

Remember that the first run with a real credential is followed by our team before the connector is fully released.

Plan and permissions#

  • Plano: core of the product (connectors are part of all plans; the limit is the number of sources of the plan).
  • Acesso: requires an active workspace — if the subscription is overdue, suspended, or canceled, the run is blocked.
  • Desligamento: the ingestion run can be temporarily turned off (maintenance or incident). When that happens, the UI indicates the feature is unavailable at the moment.

Prerequisites#

  • An RD Station Marketing account with access to the data you want to ingest.
  • On the RD Station App Store (appstore.rdstation.com), create an app, authorize it in your account and exchange the code for the access/refresh token pair (POST /auth/token). Provide Client ID, Client Secret and the Refresh token; secrets are encrypted (AES-256-GCM) and never shown again. For the contacts table, provide the ID of a segmentation.

Credentials#

Authentication method: OAuth 2.0 (client id/secret + refresh token). All secrets are encrypted (AES-256-GCM) and never displayed again. If authorization expires, just reconnect — the source and history are preserved.

Sensitive fields. They are encrypted (AES-256-GCM) and never remain in the config of the connection, in the pipeline definition, in the export or in the DAG. By default the encrypted value is stored in the database; moving the credential of this connection to the external credential vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Client Secret (clientSecret)
  • Refresh token (refreshToken) — Issued when authorizing the app in your RD Station Marketing account. It is not rotated at every renewal; if revoked, reconnect — there is no need to recreate the source.

Secrets are never re-displayed and go through redaction in every error/log (raw token, URL-encoded and in JSON).

Form fields#

CampoRótuloTipoObrigatórioObservação
clientIdClient IDtextyesIdentifier of the app created in the RD Station App Store.
clientSecret 🔒Client Secretpassword/secretyessecret (encrypted; external vault optional)
refreshToken 🔒Refresh tokenpassword/secretyessecret (encrypted; external vault optional); Issued when authorizing the app in your RD Station Marketing account. It is not rotated at every renewal; if revoked, reconnect — there is no need to recreate the source.
segmentationIdSegmentation IDtextnoOptional. With the ID (Contacts → Segmentações → number in the URL), the contacts_segmentacao table brings the contacts from that segmentation.

Step by step#

  1. No menu Dados → Conexões, use Nova conexão.
  2. Choose RD Station Marketing in the catalog.
  3. Fill in the form fields (see table above).
  4. Use Testar conexão. The result is shown broken down into Conectividade, Autenticação and Listagem/leitura — each with OK, Failed, Not applicable or Not tested. A capability with no test of its own for this connector shows as Not applicable, and Not applicable never counts as success.
  5. Use Salvar conexão. Saving does NOT start any ingestion.
  6. In the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. In review, Publicar (agenda desligada) creates version 1 without running anything. Afterwards, Ativar agenda and Executar agora are separate actions.

Example — connection test#

Example configuration (all values fictitious; secrets appear masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
clientId = exemplo-client-id-ficticio
clientSecret = •••••• (cifrado — nunca exibido)
refreshToken = •••••• (cifrado — nunca exibido)
segmentationId = <segmentationId>

Expected result#

Testar conexão returns the list of discovered tables/resources. After the first load, the rows appear in the Bronze layer of your workspace, ready for the pipeline.

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~0.3 GB/month (catalog estimate, not measured).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (chargeable).

Security#

  • Scope per workspace: each customer reads and writes only to their own datalake (<prefixo>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being written. The external credential vault is optional and enabled per connection; without it, the encrypted value stays in the database. Changing the value here does NOT revoke the credential at the origin.
  • Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
  • Production does not fake: a path that would fall into a mock triggers the production guard (explicit failure instead of simulating success).

Common errors#

  • Credential rejected (401/403) — the provider did not accept the credential: expired, revoked, or lacking required permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Rate limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, report) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If this happens in consecutive runs, open a support ticket specifying the connector and the resource.
  • Empty records path — the response arrived without records in the expected place. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network issues before scheduling.
  • Monitor runs in the connector observability (error rate, p50/p95, freshness).
  • A schema change at the source is signaled by schema drift (new column = info; removed column/type changed = attention).

Related#


Last review: 2026-10-04. Datasheet automatically generated from the product connectors catalog.

Related links