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 milestone ID. It is useful in project management scenarios where users want to fetch all tasks linked to a particular milestone within a project, enabling better tracking and organization of work items related to that milestone.
For example, a project manager can use this node to list all tasks under a milestone to monitor progress or generate reports on milestone completion status.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of results to retrieve when fetching multiple tasks (pagination support). Defaults to 1. |
| Milestone_id | The unique identifier of the milestone for which to retrieve associated tasks. |
Output
The node outputs JSON data representing the tasks retrieved from the Cloodo API for the specified milestone. Each task object typically includes details such as task ID, name, status, assigned users, deadlines, and other relevant metadata defined by the Cloodo system.
If the API supports it, pagination information may also be included to navigate through multiple pages of tasks.
No binary data output is indicated in the source code.
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
- Invalid or missing milestone ID: Ensure the
Milestone_idproperty is correctly set; otherwise, the API may return errors or empty results. - Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Pagination issues: If many tasks exist, use the
Pageproperty to paginate through results. - API connectivity problems: Check network access to the Cloodo API endpoint and confirm no firewall or proxy blocks exist.
Common error messages might include unauthorized access, resource not found, or invalid parameters. Resolving these usually involves checking credentials, input values, and API availability.
Links and References
- Cloodo CRM API Documentation (assumed base URL, consult official docs for detailed endpoints)
- n8n documentation on HTTP Request Node for understanding API integrations