Overview
This node integrates with RD Station CRM to retrieve "Motivos de Perda" (Loss Reasons) data. It allows users to either list all loss reasons or get details of a specific loss reason by its ID. This is useful for sales and CRM automation workflows where understanding why deals are lost can help improve sales strategies, reporting, and follow-up actions.
Common scenarios:
- Automatically fetching all active loss reasons to update internal dashboards.
- Retrieving detailed information about a specific loss reason to analyze why a particular deal was lost.
- Filtering loss reasons by status or sorting them by name or creation date for better data management.
Practical example:
A sales manager wants to generate a weekly report on the most common reasons deals were lost. Using this node, they can list all active loss reasons sorted by creation date and integrate that data into their reporting system.
Properties
| Name | Meaning |
|---|---|
| Parâmetros de Listagem | Collection of parameters to customize the listing of loss reasons: |
| - Limite | Maximum number of loss reasons to return |
| - Página | Page number to return |
| - Ordenação | Field to sort results by; options: "Nome" (name), "Data de Criação" (created_at) |
| - Direção da Ordenação | Sort direction; options: "Ascendente" (ascending), "Descendente" (descending) |
| - Status | Filter loss reasons by status; options: "Ativo" (active), "Inativo" (inactive), "Todos" (all) |
Output
The node outputs an array of JSON objects representing loss reasons retrieved from RD Station CRM.
- For the Listar (getAll) operation, the output JSON contains a list of loss reasons with their properties as returned by the API, such as IDs, names, statuses, creation dates, etc.
- For the Obter (get) operation, the output JSON contains the details of a single loss reason identified by the provided ID.
No binary data is output by this node.
Dependencies
- Requires an API authentication token credential configured in n8n to access RD Station CRM's API.
- The node makes HTTP GET requests to
https://crm.rdstation.com/api/v1/deal_lost_reasonsendpoint. - Proper network connectivity to RD Station CRM API is necessary.
Troubleshooting
- Missing or invalid loss reason ID: When using the "Obter" operation, if the ID parameter is empty or invalid, the node throws an error indicating a valid loss reason ID must be provided.
- API request failures: Network issues or invalid credentials may cause request errors. Ensure the API key credential is correctly set up and has sufficient permissions.
- Empty results: If filters like status or pagination parameters are too restrictive, the node might return empty lists. Adjust parameters accordingly.
- Rate limiting or API limits: Frequent calls might hit API rate limits; consider adding delays or handling retries.
Links and References
- RD Station CRM API Documentation
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)