Actions62
- Client Actions
- ClientDetail Actions
- Engagement Actions
- Estimate 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 tasks associated with a specific project. The "Get Task By Project ID" operation fetches tasks linked to a given project identifier, supporting pagination to handle large sets of tasks efficiently.
Common scenarios for this node include:
- Displaying or processing all tasks under a particular project in workflow automation.
- Synchronizing project task data from Cloodo CRM into other systems.
- Generating reports or dashboards based on project-specific tasks.
For example, a user might automate fetching all tasks for a project before sending reminders or updating statuses in another tool.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of results to retrieve (for paginated responses). Defaults to 1. |
| Project_id | The unique identifier of the project whose tasks are to be fetched. |
Output
The node outputs JSON data containing the list of tasks retrieved from the Cloodo CRM API for the specified project. Each task object typically includes details such as task name, status, assigned users, deadlines, and other relevant metadata as provided by the API.
If the API supports binary data related to tasks (e.g., attachments), the node would also output this in a binary format, but based on the static code, the primary output is JSON task data.
Dependencies
- Requires an active connection to the Cloodo CRM API.
- Needs an API authentication token or key configured in the node's credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/.
Troubleshooting
- Invalid Project ID: If the provided project ID does not exist or is incorrect, the API may return an error or empty result. Verify the project ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up.
- Pagination Issues: Requesting pages beyond the available range may return empty results. Adjust the "Page" property accordingly.
- Network or API Downtime: Connectivity issues or API service interruptions can cause request failures. Check network connectivity and Cloodo CRM service status.
Links and References
- Cloodo CRM API Documentation (assumed base URL; consult official docs for detailed API endpoints)
- n8n Documentation on Creating Custom Nodes