RD Station Marketing

RD Station Marketing is a marketing automation platform widely used across Latin America to capture and manage leads, publish landing pages and pop-ups, run email campaigns, and orchestrate automation workflows. Its API exposes contacts, conversion and funnel analytics, email statistics, landing pages, segmentations, and workflows, and lets you create or update contacts, record conversions, and track custom events. Use this connector to ingest RD Station Marketing data into Nexla or to push contacts, events, and conversions back into RD Station Marketing.

Power end-to-end data operations for your RD Station Marketing API with Nexla. Our bi-directional RD Station Marketing connector is purpose-built for RD Station Marketing, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to RD Station Marketing or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your RD Station Marketing workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

RD Station Marketing authenticates API requests using OAuth 2.0. Before creating a credential in Nexla, you need a Client ID and Client Secret issued to an application registered in the RD Station App Store. Nexla uses these to run the authorization-code flow, exchanging an authorization code for the access and refresh tokens that authorize subsequent API calls.

To obtain your credentials:

1. Sign in to your RD Station account with a user that has access to the App Store / App Publisher area.

2. Register a new application in the RD Station App Store (App Publisher). Each registered application receives its own client_id and client_secret, and each set of credentials grants access to a single RD Station Marketing account.

3. Copy the generated Client ID and Client Secret. Store the Client Secret securely, as it is sensitive information used to authenticate your application when exchanging tokens.

4. When you connect the application to an RD Station Marketing account, an authorization code is generated and exchanged (one time) for an access_token and a refresh_token. Nexla performs this exchange for you during credential creation and refreshes the access token as needed.

For full details on registering an application and the OAuth 2.0 flow, see the RD Station Developers documentation.

Authenticate

Credentials required

OAuth 2.0 authorization-code (3-legged) flow. Supply your registered application's Client ID and Client Secret; Nexla completes the authorization exchange and manages the resulting access and refresh tokens.

Field	Required	Secret	Description
Authorization URL	No	No	The URL endpoint where users authenticate and authorize access.
Client ID	Yes	Yes	A unique public identifier assigned to your RD Station application.
Token URL	No	No	The URL endpoint where authorization codes are exchanged for access tokens.
Client Secret	No	Yes	A private key used to authenticate your application when requesting tokens.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Confirm the Authorization URL. This is the endpoint where users authenticate and authorize access, and it defaults to https://api.rd.services/auth/dialog.

4. Enter the Client ID issued to your registered RD Station application.

5. Enter the Client Secret issued to your registered RD Station application. This value must be kept confidential.

6. Confirm the Token URL used to exchange the authorization code for an access token. This defaults to https://api.rd.services/auth/token.

7. Complete the OAuth authorization flow by following the prompts to authorize Nexla to access your RD Station Marketing account. Nexla handles the token exchange and refreshes the access token automatically.

8. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the RD Station Marketing connector tile, then select the credential that will be used to connect to RD Station Marketing, and click Next; or, create a new RD Station Marketing credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common RD Station Marketing endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Analytics Conversions

This endpoint template retrieves conversion analytics from your RD Station Marketing account. Use it to bring aggregated conversion metrics into Nexla for reporting and analysis.

• Data is returned as JSON from the analytics conversions endpoint.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Analytic Emails

This endpoint template retrieves email analytics from your RD Station Marketing account. Use it to ingest email performance metrics for reporting and analysis.

• Data is returned as JSON from the analytics emails endpoint.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Analytics Funnel

This endpoint template retrieves funnel analytics from your RD Station Marketing account. Use it to bring funnel-stage metrics into Nexla for reporting and analysis.

• Data is returned as JSON from the analytics funnel endpoint.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Analytics Workflow Emails Statistics

This endpoint template retrieves statistics for emails sent by automation workflows in your RD Station Marketing account. Use it to analyze workflow email performance.

• Data is returned as JSON from the workflow emails analytics endpoint.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Emails

This endpoint template retrieves the emails in your RD Station Marketing account. Use it to ingest email records for analysis, reporting, or integration purposes.

• This endpoint is paginated. Nexla automatically pages through the results until no further data is returned.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Embeddables

This endpoint template retrieves the embeddable forms in your RD Station Marketing account. Use it to ingest embeddable records for analysis, reporting, or integration purposes.

• This endpoint is paginated. Nexla automatically pages through the results until no further data is returned.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Fields

This endpoint template retrieves the contact fields defined in your RD Station Marketing account. Use it to understand the contact schema or to synchronize field definitions.

• Data is returned as JSON from the contact fields endpoint.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Landing Pages

This endpoint template retrieves the landing pages in your RD Station Marketing account. Use it to ingest landing page records for analysis, reporting, or integration purposes.

• This endpoint is paginated. Nexla automatically pages through the results until no further data is returned.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Popups

This endpoint template retrieves the pop-ups in your RD Station Marketing account. Use it to ingest pop-up records for analysis, reporting, or integration purposes.

• This endpoint is paginated. Nexla automatically pages through the results until no further data is returned.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Segmentations

This endpoint template retrieves the contact segmentations in your RD Station Marketing account. Use it to ingest segmentation records for analysis, reporting, or integration purposes.

• This endpoint is paginated. Nexla automatically pages through the results until no further data is returned.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Workflows

This endpoint template retrieves the automation workflows in your RD Station Marketing account. Use it to ingest workflow records for analysis, reporting, or integration purposes.

• This endpoint is paginated. Nexla automatically pages through the results until no further data is returned.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] Get Contact By Identifier

This endpoint template queries a single contact by identifier. Use it to fetch one contact record for enrichment, lookups, or targeted synchronization.

• Provide the Identifier — the identifier type to look up the contact by: uuid, email, or phone.
• Provide the Value — the identifier value (the uuid, email, or phone) of the contact to query.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

[Rest API] List Contact Events

This endpoint template queries the conversion or opportunity events recorded for a contact. Use it to ingest a contact's event history for analysis or integration purposes.

• Provide the Uuid — the contact's unique uuid.
• Provide the Event Type — the event type to filter by: CONVERSION or OPPORTUNITY.
• This endpoint is paginated. Nexla automatically pages through the results until no further data is returned.

For detailed information about the response structure and available fields, see the RD Station Developers documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

RD Station Marketing data sources can also be manually configured to ingest data from any valid RD Station Marketing API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new RD Station Marketing data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the RD Station Marketing destination, and select the Send to Destination option from the menu. Select the RD Station Marketing connector from the list of available destination connectors, then select the credential that will be used to connect to RD Station Marketing, and click Next; or, create a new RD Station Marketing credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common RD Station Marketing endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Or Update Contact

This endpoint template creates or updates a lead/contact record in RD Station Marketing using records from a Nexset. Use it to keep your RD Station Marketing contacts in sync with data from your Nexla flows.

• Each record from your Nexset is sent as JSON in the request body to create or update a contact.

The record structure must match the format expected by the RD Station Marketing API. For detailed information about the request body and available fields, see the RD Station Developers documentation.

[Rest API] Update Contact

This endpoint template partially updates an existing contact by email or UUID identifier using records from a Nexset. Use it to apply targeted updates to specific contacts.

• Provide the Identifier — the identifier type to look up the contact by: uuid, email, or phone.
• Provide the Value — the identifier value (the uuid, email, or phone) of the contact to update.
• Each record from your Nexset is sent as JSON in the request body to update the matched contact.

The record structure must match the format expected by the RD Station Marketing API. For detailed information about the request body and available fields, see the RD Station Developers documentation.

[Rest API] Create Event

This endpoint template tracks a custom engagement event for a contact in RD Station Marketing using records from a Nexset. Use it to record activity events driven by your Nexla flows.

• Each record from your Nexset is sent as JSON in the request body to create an event.

The record structure must match the format expected by the RD Station Marketing API. For detailed information about the request body and available fields, see the RD Station Developers documentation.

[Rest API] Create Conversion

This endpoint template records a conversion event (for example, a form submission) for a prospect in RD Station Marketing using records from a Nexset. Use it to register conversions captured in your Nexla flows.

• Each record from your Nexset is sent as JSON in the request body to create a conversion.

The record structure must match the format expected by the RD Station Marketing API. For detailed information about the request body and available fields, see the RD Station Developers documentation.

[Rest API] Create Events Batch

This endpoint template submits a batch of engagement events for multiple contacts in a single request using records from a Nexset. Use it for higher-throughput event tracking.

• Records from your Nexset are sent as JSON in the request body to the batch events endpoint.

The record structure must match the format expected by the RD Station Marketing API. For detailed information about the request body and available fields, see the RD Station Developers documentation.

[Rest API] Delete Contact

This endpoint template deletes a contact by uuid, email, or phone identifier using records from a Nexset. Use it to remove contacts from RD Station Marketing based on your Nexla flows.

• Provide the Identifier — the identifier type to look up the contact by: uuid, email, or phone.
• Provide the Value — the identifier value (the uuid, email, or phone) of the contact to delete.

Deleting a contact is irreversible. For detailed information about this operation, see the RD Station Developers documentation.

[Rest API] Insert Workflow Leads

This endpoint template inserts leads (by email or phone) into an automation workflow using records from a Nexset. Use it to add contacts to a workflow from your Nexla flows.

• Provide the Id — the workflow's unique identifier.
• Each record from your Nexset is sent as JSON in the request body to insert leads into the specified workflow.

The record structure must match the format expected by the RD Station Marketing API. For detailed information about the request body and available fields, see the RD Station Developers documentation.

Manual configuration

RD Station Marketing destinations can also be manually configured to send data to any valid RD Station Marketing API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

RD Station Marketing APIs expect JSON in the request body for most operations. For update or delete operations, include the contact identifier (uuid, email, or phone) in the request URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured RD Station Marketing endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the RD Station Marketing endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.