RD Station

Consume RD Station API

Actions5

Call Finished Actions
- New Conversion
Conversion Actions
- New Conversion
Lost Actions
- New Conversion
Opportunity Actions
- New Conversion
Sale Actions
- New Conversion

Overview

This n8n node integrates with the RD Station API to register a "Call Finished" event as a new conversion. It is designed for scenarios where you want to track completed calls (either inbound or outbound) and associate them with leads in your RD Station account. This is particularly useful for sales, support, or marketing teams who need to log call outcomes and enrich lead data automatically.

Practical Example:
When a call tracking system detects that a call has ended, this node can be used to send the call details (such as caller number, type of call, and any custom fields) directly to RD Station, updating the lead's record and triggering further automation or analytics.

Properties

Below are the supported input properties for the "Call Finished" resource with the "New Conversion" operation:

Display Name	Type	Description
Email	String	Primary email for the lead. Required.
Call From Number	String	Number of Call Tracking. The phone number from which the call originated. Required.
Call Type	Options	Call type: "Inbound" or "Outbound". Indicates whether the call was incoming or outgoing. Default: Outbound.
Call Status	Hidden	Always set to "in_progress". Used internally to indicate the status of the call event.
Additional Fields	Collection	Allows adding custom fields not predefined. Useful for sending extra information about the call or lead.
- Custom Fields	FixedCollection	Add one or more custom fields. Each field includes:
-- Field Name on RD Station	String	The identifier of the custom field in RD Station (must start with "cf_").
-- Field Value	String	The value to assign to the custom field.

Output

The node outputs a JSON object representing the result of the API request to RD Station. The structure typically includes:

{
  // ...fields returned by the RD Station API after registering the event
}

The exact output fields depend on the RD Station API response.
If an error occurs and "Continue On Fail" is enabled, the output will include:
```
{
  "json": {},
  "error": "Error message",
  "itemIndex": 0
}
```

Binary Data:
This node does not output binary data; all output is in JSON format.

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 required beyond standard n8n credential setup.

Troubleshooting

Common Issues:

Missing Required Fields: If "Email" or "Call From Number" is missing, the node will throw an error.
Invalid Custom Field Identifiers: Custom fields must use the correct identifier format (e.g., cf_fieldname). Incorrect identifiers may cause the API to reject the request.
API Authentication Errors: Invalid or expired OAuth2 credentials will result in authentication errors.
RD Station API Errors: Any issues with the RD Station API (rate limits, downtime, etc.) will be reflected in the error message.

Error Messages:

"Missing required parameter": Ensure all required fields are filled.
"Invalid field identifier": Check that custom field names match those defined in RD Station.
"401 Unauthorized": Verify your OAuth2 credentials.
"API request failed": Review the error details for more information.