Actions5
- Contact Actions
- Event Actions
Overview
This node integrates with the RD Station Marketing API to register a standard conversion event associated with a contact. It is useful for tracking specific conversion actions (like form submissions, purchases, or sign-ups) tied to a contact's email address within RD Station Marketing.
Typical use cases include:
- Recording when a contact completes a desired action on your website or app.
- Tracking marketing campaign effectiveness by logging conversions.
- Enriching contact profiles with conversion data for segmentation and follow-up.
For example, you can trigger this node after a user fills out a form, sending the conversion event with the user's email and conversion identifier to RD Station Marketing.
Properties
| Name | Meaning |
|---|---|
| Conversion Identifier | The name of the conversion event to register (e.g., "purchase", "signup"). |
| Contact's email address to associate the conversion event with. | |
| Additional Fields | Optional extra information about the contact or conversion event. Includes: |
| - Bio | Notes about the contact. |
| - Birthday Date | Contact's birthdate. |
| - City | Contact's city. |
| - Country | Contact's country. |
| - Custom Fields | Custom key-value pairs for additional properties not predefined in the node. |
| URL to the contact's Facebook profile. | |
| - Job Title | Contact's job position or title. |
| URL to the contact's LinkedIn profile. | |
| - Mobile Phone | Contact's mobile phone number. |
| - Name | Contact's full name. |
| - Phone | Contact's personal phone number. |
| - State | Contact's state or region. |
| - Tags | Comma-separated list of tags to assign to the contact. |
| URL to the contact's Twitter profile. | |
| - Website | Contact's website URL. |
Output
The node outputs the JSON response from the RD Station Marketing API after registering the conversion event. This typically includes confirmation details of the event registration.
The output structure contains:
json: An object representing the API response for the conversion event.pairedItem: Metadata linking the output to the input item index.
No binary data is produced by this operation.
Dependencies
- Requires an API authentication credential configured in n8n to access the RD Station Marketing API.
- The node uses HTTP requests to communicate with the RD Station Marketing platform endpoints.
- No additional external dependencies are required beyond the configured API credential.
Troubleshooting
- Missing Required Fields: The node requires both the "Conversion Identifier" and "Email" fields. Omitting these will cause errors.
- Invalid Email Format: Ensure the email provided is valid; otherwise, the API may reject the request.
- API Authentication Errors: Verify that the API credential is correctly set up and has necessary permissions.
- Network Issues: Connectivity problems can cause request failures; check network access to RD Station Marketing API.
- Error Messages: If the API returns an error, it will be included in the node output if "Continue On Fail" is enabled. Review the error message for details such as invalid parameters or rate limits.
Links and References
- RD Station Marketing API Documentation
- n8n Expressions Documentation (for using expressions in custom fields)