Overview
This node integrates with RD Station CRM to retrieve information about lead sources ("fontes"). It allows users to either list all available lead sources or obtain details of a specific source by its ID. This is useful for workflows that need to dynamically access or process lead source data from RD Station CRM, such as syncing lead sources with other systems, reporting, or filtering leads based on their origin.
Practical examples:
- Automatically fetching all active lead sources to populate dropdowns in other applications.
- Retrieving detailed information about a particular lead source by its ID to enrich lead data or trigger conditional logic.
Properties
| Name | Meaning |
|---|---|
| ID da Fonte | The unique identifier of the lead source to be retrieved. Must be provided when using the "Obter" (Get) operation on the "Fonte" resource. |
Output
The node outputs an array of JSON objects representing the lead source(s) data returned by the RD Station CRM API:
For the Obter (Get) operation:
The output JSON contains the details of a single lead source identified by the given ID.For the Listar (Get All) operation (not requested but present in code):
The output JSON contains a list of lead sources, potentially filtered and paginated according to parameters.
Each output item includes a json field with the API response body containing the lead source data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for RD Station CRM to authenticate requests.
- The node makes HTTP GET requests to the RD Station CRM API endpoint at
https://crm.rdstation.com/api/v1/deal_sources. - Proper configuration of the RD Station CRM API credentials within n8n is necessary.
Troubleshooting
Missing or invalid source ID: If the "ID da Fonte" property is empty or invalid when performing the "Obter" operation, the node will throw an error indicating that a valid source ID must be provided. Ensure the ID is correctly set.
API authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate. Verify the API key and credential setup in n8n.
Network or API errors: Any network issues or API downtime may cause request failures. Check connectivity and RD Station CRM service status.
Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.