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 call finished conversions. Specifically, it supports creating a new conversion event when a call finishes, capturing details such as the lead's email, call tracking number, call type (inbound or outbound), and call status. It also allows adding custom fields to enrich the event data. This node is useful for marketing automation and CRM workflows where tracking call outcomes as conversions is important, such as logging leads generated from phone calls or tracking call campaign effectiveness.

Use Case Examples

  1. Register a new call finished conversion event with the lead's email, call tracking number, and call type.
  2. Add custom fields to the call finished conversion event to capture additional lead information not predefined in the node.
  3. Use this node in a workflow to automatically log call outcomes as conversions in RD Station for further marketing and sales analysis.

Properties

Name Meaning
Email Primary email for the lead, required to identify the contact in RD Station.
Call From Number Number of Call Tracking, required to specify the phone number associated with the call.
Call Type Type of the call, either Inbound or Outbound, to classify the call direction.
Call Status Status of the call, hidden field defaulting to 'in_progress'.
Additional Fields Collection of additional fields including custom fields to set values not predefined in the node.

Output

JSON

  • event_type - Type of event sent to RD Station, e.g., CALL_FINISHED.
  • event_family - Event family, fixed as 'CDP' for customer data platform events.
  • payload
    • email - Email of the lead associated with the call finished event.
    • call_from_number - Phone number from which the call was made.
    • call_type - Type of the call, inbound or outbound.
    • call_status - Status of the call, typically 'in_progress'.
    • customFields - Optional custom fields added to the event payload for additional data.

Dependencies

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

Troubleshooting

  • Common issues include missing required fields such as email or call_from_number, which will cause the API request to fail.
  • Errors may occur if custom field names do not follow the required prefix 'cf_' or if invalid values are provided.
  • Network or authentication errors can happen if the OAuth2 credentials are not properly configured or expired.

Links

Discussion