Actions62
- Engagement Actions
- Estimate Actions
- Client Actions
- ClientDetail Actions
- Lead Actions
- Lead Agent Actions
- Lead Category Actions
- Lead Source Actions
- Lead Status Actions
- Proposal Actions
- Project Actions
- Task Actions
- Note Actions
Overview
This node integrates with the Cloodo CRM API to retrieve data related to various resources, including tasks. Specifically, for the Task resource with the Get operation, it fetches detailed information about a single task identified by its unique ID. This is useful in scenarios where you need to pull specific task details from Cloodo CRM into your workflow, such as displaying task status, deadlines, or descriptions for project management automation.
Practical examples:
- Fetching a task's details to update a project dashboard.
- Retrieving task information before sending notifications or reminders.
- Integrating task data into reporting tools or other systems.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the task to retrieve. You must provide this ID to specify which task's details to fetch. |
Output
The node outputs JSON data representing the task object retrieved from the Cloodo CRM API. This JSON typically includes fields such as task name, description, status, assigned users, due dates, and other metadata associated with the task.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the task, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Cloodo CRM API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/.
Troubleshooting
- Missing or invalid ID: If the ID property is empty or incorrect, the API will likely return an error indicating that the task was not found. Ensure the ID is valid and corresponds to an existing task.
- Authentication errors: If the API key or token is missing or invalid, the node will fail to authenticate. Verify that the credential is correctly set up in n8n.
- Network issues: Connectivity problems can cause request failures. Check network access to the Cloodo API endpoint.
- API changes: If the Cloodo API changes its endpoints or response formats, the node might fail or produce unexpected results. Keep the node updated accordingly.
Links and References
- Cloodo CRM API Documentation (Assumed base URL; consult official docs for detailed API reference)
- n8n documentation on creating custom nodes