Overview
This node integrates with RD Station CRM to manage tasks related to deals and users. Specifically, the Listar (List) operation under the Tarefa (Task) resource allows users to retrieve multiple tasks from RD Station CRM based on various filtering and sorting parameters.
Common scenarios where this node is beneficial include:
- Fetching pending or completed tasks assigned to specific users or linked to particular deals.
- Retrieving tasks within a date range for reporting or monitoring purposes.
- Sorting tasks by due date or creation date in ascending or descending order to prioritize work.
For example, a sales manager could use this node to list all pending tasks assigned to their team members for the current month, sorted by due date ascending, to organize follow-ups efficiently.
Properties
| Name | Meaning |
|---|---|
| Limite | Maximum number of tasks to return (number). |
| Página | Page number of results to return (number). |
| ID do Negócio | Filter tasks by a specific deal ID (string). |
| ID do Usuário | Filter tasks by the responsible user ID (string). |
| Status | Filter tasks by status: "Pendentes" (pending), "Concluídas" (done), or "Todas" (all). |
| Data Inicial | Start date to filter tasks (format YYYY-MM-DD) (string). |
| Data Final | End date to filter tasks (format YYYY-MM-DD) (string). |
| Ordenação | Field to sort results by: "Data de Vencimento" (due_date) or "Data de Criação" (created_at). |
| Direção da Ordenação | Sort direction: "Ascendente" (asc) or "Descendente" (desc). |
Output
The output is an array of JSON objects representing tasks retrieved from RD Station CRM. Each item corresponds to a task and includes all fields returned by the API, such as task ID, title, type, due date, user assignment, status, and other metadata.
No binary data is output by this node.
Example output snippet (simplified):
[
{
"id": "12345",
"title": "Follow up call",
"type": "call",
"due_date": "2024-06-15",
"user_id": "67890",
"status": "pending",
...
},
...
]
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/tasks. - Proper network access to RD Station CRM API is necessary.
Troubleshooting
- Missing or invalid task ID: When using operations that require a task ID (e.g., get or update), ensure the ID is provided and valid; otherwise, the node throws an error indicating the missing ID.
- Required fields missing: For creating tasks, the node requires a deal ID, task title, and task type. Omitting these will cause errors.
- Empty update data: When updating a task, at least one field must be provided to update; otherwise, an error is thrown.
- API authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Rate limits or network issues: If requests fail due to rate limiting or connectivity problems, consider adding retry logic or checking network/firewall settings.