Overview
This node integrates with RD Station CRM to retrieve information about sales pipelines ("Funis") and their stages ("Etapas"). Specifically, the "Funil" resource with the "Listar" operation allows users to list all sales pipelines available in their RD Station CRM account. This is useful for automating reporting, syncing pipeline data with other systems, or dynamically selecting pipelines in workflows.
Practical examples:
- Automatically fetch all active sales pipelines to display in a dashboard.
- Use the list of pipelines to trigger different workflow branches based on pipeline status or creation date.
- Export pipeline data periodically for backup or analysis.
Properties
Name | Meaning |
---|---|
Parâmetros de Listagem | Collection of parameters to control listing behavior: |
- Limite | Maximum number of pipelines to return (default 50) |
- Página | Page number of results to return (default 1) |
- Ordenação | Field to order results by: "Nome" (name) or "Data de Criação" (creation date) |
- Direção da Ordenação | Direction of ordering: "Ascendente" (ascending) or "Descendente" (descending) |
- Status | Filter pipelines by status: "Ativo" (active), "Inativo" (inactive), or "Todos" (all) |
Output
The node outputs an array of JSON objects representing the pipelines retrieved from RD Station CRM. Each item corresponds to one pipeline and contains all its properties as returned by the API, such as pipeline ID, name, status, creation date, and other metadata.
The output structure is:
[
{
"json": {
// Pipeline object fields as provided by RD Station CRM API
},
"pairedItem": {
"item": <index_of_input_item>
}
}
]
No binary data is produced 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 or invalid pipeline ID: When using operations that require a specific pipeline ID, if the ID is not provided or invalid, the node throws an error indicating a valid pipeline ID must be supplied.
- API authentication errors: If the API key credential is missing, invalid, or expired, requests will fail. Ensure the credential is correctly set up and has proper permissions.
- Rate limits or network issues: The RD Station CRM API may impose rate limits or experience downtime. In such cases, the node may throw request errors. Retrying after some time or checking API status is recommended.
- Incorrect parameter values: Providing invalid values for pagination or filtering parameters may result in empty responses or errors. Verify parameter correctness.