RD Station icon

RD Station

Consume RD Station API
Join our community

Actions5

Overview

This node integrates with the RD Station API to register new events related to marketing and sales processes, specifically handling new conversions, opportunities, sales, lost opportunities, and finished calls. It is useful for automating lead and contact management workflows by sending event data such as email, funnel status, call details, and custom fields to RD Station. For example, it can mark a contact as an opportunity in a sales funnel or log a finished call with call tracking information.

Use Case Examples

  1. Register a new lead conversion with email and job title.
  2. Mark a contact as an opportunity in a specific sales funnel.
  3. Log a finished call with call type and call tracking number.

Properties

Name Meaning
Email Primary email for the lead, used to identify the contact in RD Station.
Funnel Name Name of the funnel to which the contact should be marked as opportunity, won, or lost, depending on the resource type.
Call Status Internal status of the call, defaulting to 'in_progress', used when logging finished calls.

Output

JSON

  • event_type - Type of event sent to RD Station, e.g., CONVERSION, OPPORTUNITY.
  • event_family - Event family, always 'CDP' for these events.
  • payload
    • email - Email of the lead/contact.
    • funnel_name - Funnel name for opportunity, sale, or lost events.
    • value - Value of the won opportunity (only for sales).
    • reason - Reason for lost opportunity (only for lost events).
    • call_from_number - Phone number from which the call was made (only for finished calls).
    • call_type - Type of call, inbound or outbound (only for finished calls).
    • call_status - Status of the call, typically 'in_progress' (only for finished calls).
    • customFields - Custom fields added to the payload for conversion or call_finished events.

Dependencies

  • Requires an OAuth2 API credential for RD Station to authenticate requests.

Troubleshooting

  • Common issues include missing required parameters such as email or funnel_name, which will cause the API request to fail.
  • Errors may occur if the funnel name or conversion identifier does not exist or is misspelled in RD Station.
  • Network or authentication errors can happen if the OAuth2 token is invalid or expired; re-authentication may be required.
  • If custom fields are used, ensure the field IDs are correctly prefixed with 'cf_' and exist in RD Station to avoid payload rejection.

Links

Discussion