Cloodo Project icon

Cloodo Project

Get data from Cloodo Worksuite API

Overview

The node "Cloodo Project" integrates with the Cloodo Worksuite API to retrieve and manage project-related data. It supports multiple resources such as Projects, Milestones, Tasks, Project Admins, and Time Logs. Specifically, for the Project Payment operation, it fetches payment information related to projects.

This node is beneficial in scenarios where users need to automate the retrieval of project payment details from Cloodo Worksuite, for example:

  • Generating financial reports based on project payments.
  • Syncing payment data with accounting or ERP systems.
  • Monitoring payment statuses for ongoing projects.

Properties

Name Meaning
Resource Selects the type of data to work with (e.g., Project, Milestone, Task, Project Admin, Time Log).
Operation The action to perform on the selected resource (e.g., getPayment for Project resource).
ID The unique identifier of the project or related entity to fetch or manipulate data for.
Page The page number for paginated results when retrieving multiple records.
Additional Fields Optional parameters to refine the request:
- Limit Number of items to return per page; options are 10, 25, or 50.
- From Date Start date filter for the payment data (format expected by API).
- To Date End date filter for the payment data (format expected by API).

Output

The node outputs JSON data containing the requested project payment information. The structure typically includes payment details such as amounts, dates, statuses, and related project identifiers. The exact fields depend on the API response but generally provide comprehensive payment records.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Cloodo Worksuite API.
  • The base URL for API requests is https://erp-amz.cloodo.com/v4.
  • Proper configuration of the API credential within n8n is necessary to authorize requests.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect or missing project ID may result in empty or error responses.
    • Date filters (From Date, To Date) must be in the correct format expected by the API; otherwise, the API may reject the request or return no data.
    • Pagination parameters should be set carefully to avoid missing data or excessive load.
  • Error Messages:

    • Authentication errors typically indicate invalid API keys or expired tokens; verify and update credentials.
    • "Not Found" errors suggest the provided project ID does not exist or is inaccessible.
    • Validation errors may occur if input parameters do not meet API requirements; check parameter formats and values.

Links and References

Discussion