Actions5
- Conversion Actions
- Sale Actions
- Call Finished Actions
- Lost Actions
- Opportunity Actions
Overview
This node integrates with the RD Station API to register new events related to conversions, opportunities, sales, lost deals, and finished calls. It is particularly useful for marketing and sales automation workflows where tracking lead conversions, sales funnel progress, and call outcomes is essential. For example, it can be used to log a new lead conversion with contact details, mark a contact as an opportunity or sale in a specific funnel, or record the completion of a call with relevant metadata.
Use Case Examples
- Register a new lead conversion with email, name, and job title.
- Mark a contact as a won sale with funnel name and value.
- Log a finished call with call type and status.
Properties
| Name | Meaning |
|---|---|
| Identifier | Conversion Identifier used to identify the conversion event (required for conversion resource). |
| Telefone (Celular) | Mobile phone number of the lead. |
| Nome | Full name of the lead. |
| Cargo | Job title or position of the lead. |
| Primary email address of the lead or contact (required). | |
| Call Status | Status of the call, hidden field defaulting to 'in_progress'. |
| Additional Fields | Collection of additional custom fields to set values not predefined, allowing dynamic extension of the payload. |
Output
JSON
event_type- Type of event sent to RD Station (e.g., CONVERSION, OPPORTUNITY).event_family- Event family, fixed as 'CDP' for these events.payloademail- Email of the lead/contact.conversion_identifier- Identifier for conversion events.mobile_phone- Mobile phone number of the lead.name- Name of the lead.job_title- Job title of the lead.funnel_name- Name of the funnel for opportunity, sale, or lost events.value- Value of the sale opportunity.reason- Reason for lost opportunity.call_from_number- Phone number from which the call was made.call_type- Type of call, inbound or outbound.call_status- Status of the call.customFields- Custom fields with their values added dynamically.
Dependencies
- Requires an OAuth2 API credential for RD Station to authenticate API requests.
Troubleshooting
- Common issues include missing required fields such as email or identifier, which will cause the API request to fail.
- Errors may occur if custom field names do not have the required 'cf_' prefix or if invalid field identifiers are used.
- Network or authentication errors can happen if the OAuth2 token is expired or invalid; refreshing credentials may resolve this.
Links
- RD Station - Custom Fields - Official RD Station page to manage and find identifiers for custom fields used in the payload.