Overview
This node interacts with the RD Station CRM API to retrieve information about lead sources ("fontes"). Specifically, the "Listar" (List) operation under the "Fonte" (Source) resource fetches a paginated list of lead sources from the CRM. This is useful for workflows that need to analyze, report on, or synchronize lead source data from RD Station CRM.
Common scenarios include:
- Automatically fetching all active lead sources to update an internal database.
- Filtering lead sources by status or name to trigger specific marketing automation.
- Paginating through large sets of sources for batch processing or reporting.
Example: A marketing team could use this node to list all active lead sources ordered by creation date descending, then process each source to evaluate campaign performance.
Properties
| Name | Meaning |
|---|---|
| Parâmetros de Listagem | Collection of parameters to control listing behavior: |
| - Limite | Maximum number of sources to return (number). |
| - Página | Page number to return (number). |
| - Ordenação | Field to order results by; options: "Nome" (name), "Data de Criação" (created_at). |
| - Direção da Ordenação | Direction of ordering; options: "Ascendente" (asc), "Descendente" (desc). |
| - Status | Filter sources by status; options: "Ativa" (active), "Inativa" (inactive), "Todas" (all). |
| - Termo de Busca | Search term to filter sources by name (string). |
Output
The node outputs an array of JSON objects representing the lead sources retrieved from RD Station CRM. Each item corresponds to one source or a page of sources depending on pagination.
The json output field contains the raw response body from the API, which includes details such as source ID, name, status, and creation date.
No binary data is output by this node.
Dependencies
- Requires an API key credential for RD Station CRM authentication configured in n8n.
- Makes HTTP GET requests to the RD Station CRM API endpoint at
https://crm.rdstation.com/api/v1/deal_sources. - The node uses built-in n8n helper methods to handle authenticated requests.
Troubleshooting
- Missing or invalid source ID: When using the "Obter" (Get) operation (not requested here), if the source ID is not provided or invalid, the node throws an error indicating a valid source ID is required.
- API request failures: Network issues, invalid credentials, or API limits may cause errors. Ensure the API key is valid and has sufficient permissions.
- Empty results: If filters are too restrictive (e.g., status or query), the returned list may be empty.
- Pagination issues: Setting page or limit incorrectly may result in unexpected subsets of data.
To resolve errors:
- Verify API credentials and permissions.
- Adjust listing parameters to valid values.
- Use "Continue On Fail" option in n8n to handle partial failures gracefully.