RD Station icon

RD Station

Consume RD Station API

Actions5

Overview

This node registers a new conversion event in RD Station, a marketing automation platform. It allows you to send lead information (such as email and custom fields) to RD Station, creating a new conversion record for tracking and automation purposes.

Common scenarios:

  • Automatically registering new leads from web forms or other sources into RD Station.
  • Enriching lead data with custom fields during the conversion process.
  • Integrating n8n workflows with RD Station's lead management and marketing automation features.

Practical example:
When a user submits a signup form on your website, this node can be used to create a new conversion in RD Station, including their email and any additional custom information collected.

Properties

Display Name Type Meaning
Identifier String Conversion Identifier. Used to identify the type of conversion being registered.
Email String Primary email for the lead. Required for identifying the contact in RD Station.
Call Status Hidden Always set to "in_progress" for this operation.
Additional Fields Collection Allows adding custom fields to the payload. Useful for sending extra information not covered by default properties.

Details for Additional Fields → Custom Fields:

  • Field Name on RD Station: The identifier of a custom field in RD Station (must start with cf_).
  • Field Value: The value to assign to the custom field.

Output

The node outputs a JSON object containing the response from the RD Station API after registering the conversion. The structure typically includes:

{
  "event_type": "CONVERSION",
  "event_family": "CDP",
  "payload": {
    "email": "lead@example.com",
    "conversion_identifier": "new lead",
    // ...any custom fields sent
  },
  // ...other fields returned by RD Station API
}
  • If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message and the index of the item that failed.

Dependencies

  • External Service: Requires access to the RD Station API.
  • Authentication: Needs valid RD Station OAuth2 credentials configured in n8n (rdStationOAuth2Api).

Troubleshooting

Common issues:

  • Missing required fields: Both "Identifier" and "Email" are mandatory. Omitting them will result in errors.
  • Invalid custom field names: Custom fields must use the correct identifier format (e.g., cf_fieldname). Incorrect names will cause the API to reject the request.
  • Authentication errors: Invalid or expired OAuth2 credentials will prevent successful API calls.

Error messages:

  • "Missing required parameter": Ensure all required fields are filled.
  • "Invalid field name": Check that custom field identifiers match those defined in your RD Station account.
  • "401 Unauthorized": Verify your RD Station OAuth2 credentials in n8n.

Links and References

Discussion