Overview
This node integrates with RD Station CRM to perform operations on tasks ("Tarefa"). Specifically, the "Obter" (Get) operation retrieves detailed information about a single task by its ID. This is useful when you need to fetch the current state or details of a specific task within your CRM workflow.
Common scenarios include:
- Fetching task details to display or process further in an automation.
- Verifying task status or attributes before performing updates or conditional logic.
- Integrating task data into reports or dashboards.
Example: You have a workflow that triggers when a deal is updated, and you want to retrieve the associated task's details to decide if follow-up actions are needed.
Properties
| Name | Meaning |
|---|---|
| ID da Tarefa | The unique identifier of the task to be retrieved. This is required to specify which task to obtain from RD Station CRM. |
Output
The node outputs a JSON object representing the task data as returned by the RD Station CRM API. This includes all available fields for the task such as title, type, due date, description, status, assigned user, and related deal ID.
The output structure is:
{
"id": "string",
"title": "string",
"type": "string",
"due_date": "string",
"due_time": "string",
"user_id": "string",
"description": "string",
"done": "boolean",
"deal_id": "string",
...
}
No binary data is produced by this operation.
Dependencies
- Requires an API authentication token credential configured for RD Station CRM.
- The node makes HTTP GET requests to
https://crm.rdstation.com/api/v1/tasks/{taskId}endpoint. - Proper permissions on the API key are necessary to read task data.
Troubleshooting
- Missing or invalid Task ID: If the "ID da Tarefa" property is empty or invalid, the node throws an error indicating a valid task ID must be provided.
- Authentication errors: Ensure the API credential is correctly set up and has permission to access tasks.
- Network or API errors: Check connectivity and API availability; the node will throw errors if the request fails.
- Task not found: If the specified task ID does not exist, the API may return a 404 error, which will propagate as an error in the node.
To resolve these issues:
- Verify the task ID input is correct and corresponds to an existing task.
- Confirm API credentials and permissions.
- Handle errors gracefully using the node’s "Continue On Fail" option if partial processing is acceptable.