Overview
This node integrates with RD Station CRM to perform operations on contacts. Specifically, the "Obter" (Get) operation retrieves detailed information about a single contact by its ID. This is useful when you need to fetch up-to-date contact data from your CRM for further processing, reporting, or synchronization with other systems.
Common scenarios:
- Fetching a contact's details before updating or enriching their information.
- Retrieving contact data to personalize communications or marketing campaigns.
- Integrating contact information into dashboards or analytics tools.
Practical example:
You have a workflow that triggers when a new deal is created, and you want to pull the associated contact’s full details from RD Station CRM to include in a notification email or to update another database.
Properties
| Name | Meaning |
|---|---|
| ID do Contato | The unique identifier of the contact to retrieve. This property is required for the "Obter" (get) operation. |
Output
The output is a JSON object representing the contact retrieved from RD Station CRM. It contains all available fields of the contact as stored in the CRM, such as name, emails, phones, organization, custom fields, and more.
If multiple input items are processed, the output will be an array of such JSON objects, each paired with the corresponding input item index.
No binary data is output by this node.
Dependencies
- Requires an API key credential for RD Station CRM configured in n8n.
- The node makes authenticated HTTP requests to the RD Station CRM API endpoint at
https://crm.rdstation.com/api/v1. - Proper network access to RD Station CRM API is necessary.
Troubleshooting
- Missing Contact ID: If the "ID do Contato" property is empty or not provided, the node throws an error stating that the contact ID is mandatory. Ensure this field is filled correctly.
- Invalid Contact ID: If the provided contact ID does not exist in RD Station CRM, the API may return a 404 error or similar. Verify the ID is correct.
- Authentication Errors: If the API key credential is invalid or missing, authentication errors will occur. Check the credential configuration.
- API Rate Limits or Network Issues: Temporary failures might happen due to rate limits or connectivity problems. Consider enabling "Continue On Fail" in the node settings to handle such cases gracefully.