RD Station icon

RD Station

Consume RD Station API

Actions5

Overview

This n8n node integrates with the RD Station API to register various types of events related to leads, such as conversions, opportunities, sales, lost deals, and finished calls. It is designed to automate the process of sending lead status updates and event data from your workflows directly into RD Station.

Common scenarios:

  • Automatically registering a new conversion when a user submits a form.
  • Marking a lead as an opportunity, sale, or lost based on workflow logic.
  • Logging call tracking information after a phone interaction.
  • Enriching RD Station contacts with custom fields collected elsewhere.

Practical examples:

  • When a new lead signs up on your website, use this node to create a "Conversion" event in RD Station.
  • After a sales call, automatically log the call details as a "Call Finished" event.
  • Update a lead's status to "Sale" when a deal is closed in your CRM.

Properties

Display Name Type Meaning
Call Status hidden (Default: in_progress) Used internally for call tracking; not visible to users.

Note: The provided property list only includes "Call Status". However, the node supports additional properties depending on the selected resource and operation, such as Email, Identifier, Funnel Name, Value, Reason, Call From Number, Call Type, and Additional Fields (custom fields).

Output

The node outputs a JSON object reflecting the response from the RD Station API. The structure typically includes:

{
  // ...fields returned by the RD Station API, such as:
  "event_type": "CALL_FINISHED",
  "event_family": "CDP",
  "payload": {
    "email": "lead@example.com",
    "call_from_number": "+1234567890",
    "call_type": "Outbound",
    "call_status": "in_progress"
    // ...any additional custom fields sent
  }
}
  • If the API call fails and "Continue On Fail" is enabled, the output will include an error field with the error message and the index of the failed item.

Dependencies

  • External Service: Requires access to the RD Station API.
  • Authentication: Needs valid RD Station OAuth2 credentials configured in n8n (rdStationOAuth2Api).
  • Environment: No special environment variables are required beyond standard n8n credential setup.

Troubleshooting

Common issues:

  • Missing Required Fields: If required fields (like Email or Call From Number) are missing, the node will throw an error.
  • Invalid Field Values: Supplying invalid values (e.g., non-numeric value for "Value") may cause the API request to fail.
  • Authentication Errors: Invalid or expired OAuth2 credentials will result in authentication failures.

Error messages:

  • "Missing parameter" or similar: Ensure all required fields are filled.
  • "401 Unauthorized": Check your RD Station OAuth2 credentials.
  • "Field not found": Custom field names must match those defined in RD Station, including the cf_ prefix.

How to resolve:

  • Double-check that all required input properties are set.
  • Verify your RD Station credentials in n8n.
  • For custom fields, ensure you use the correct field identifiers as per your RD Station account.

Links and References

Discussion