Actions26
- Milestone Actions
- Project Actions
- Project Admin Actions
- Task Actions
- Time Log Actions
Overview
This node integrates with the Cloodo Worksuite API to retrieve data related to project management entities. Specifically, for the "Milestone" resource and the "Get" operation, it fetches detailed information about a single milestone identified by its unique ID. This is useful in scenarios where you need to access specific milestone details within a project, such as tracking progress, deadlines, or dependencies.
Practical examples include:
- Retrieving milestone details to display in a dashboard.
- Using milestone data to trigger subsequent workflow steps based on milestone status.
- Auditing or reporting on project milestones programmatically.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the milestone to retrieve. You must provide this ID to specify which milestone's data should be fetched. |
Output
The node outputs JSON data representing the milestone object retrieved from the Cloodo Worksuite API. This typically includes fields such as milestone name, description, start and end dates, status, and any other metadata associated with the milestone.
If the node supports binary data output (not indicated here), it would represent files or attachments related to the milestone, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Cloodo Worksuite API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4. - Proper network access to the API endpoint is necessary.
Troubleshooting
- Missing or invalid ID: If the ID property is empty or incorrect, the API will likely return an error indicating that the milestone was not found. Ensure the ID is correct and corresponds to an existing milestone.
- Authentication errors: If the API key or token is missing, expired, or invalid, the node will fail to authenticate. Verify that the API credentials are correctly set up in n8n.
- Network issues: Connectivity problems or incorrect base URL configuration can cause request failures. Confirm network access and API endpoint correctness.
- API rate limits or permissions: If the user account lacks permission to access the milestone or if rate limits are exceeded, the API may return errors. Check user permissions and API usage policies.
Links and References
- Cloodo Worksuite API Documentation (Assumed; replace with actual documentation link if available)
- n8n Documentation on Creating Custom Nodes