Cloodo CRM icon

Cloodo CRM

Get data from Cloodo API

Actions62

Overview

This node integrates with the Cloodo CRM API to retrieve multiple project records based on specified criteria. It is designed to fetch a list of projects, supporting pagination and filtering by various fields such as status, category, client, member, and date ranges. This functionality is useful for scenarios where users need to display or process batches of project data, for example, generating reports, syncing projects with other systems, or monitoring project statuses.

Properties

Name Meaning
Page The page number of results to retrieve (pagination).
Limit Maximum number of projects to return per request. Options: 10, 25, 50.
Status Filter projects by their current status. Options: In Progress, Finished, Canceled, On Hold, Not Started.
Search Text string to search projects by name or other searchable fields.
Filter by Category ID Filter projects belonging to a specific category by its ID.
Filter by Client ID Filter projects associated with a specific client by its ID.
Filter by Member ID Filter projects involving a specific member by their ID.
From Date Start date to filter projects created or updated from this date onward.
To Date End date to filter projects created or updated up to this date.

Output

The node outputs JSON data containing an array of project objects matching the query parameters. Each project object includes details such as project ID, name, status, client information, category, members involved, dates, and other relevant metadata as provided by the Cloodo API.

If binary data were supported, it would typically represent attachments or files related to projects, but this node focuses on JSON data retrieval only.

Dependencies

  • Requires an active connection to the Cloodo CRM API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for API requests is https://erp-amz.cloodo.com/v4/.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect pagination parameters may result in empty responses or repeated data.
    • Filtering by IDs that do not exist will return empty results.
    • Date filters must be in a valid format recognized by the API; otherwise, no results will be returned.

  • Error Messages:

    • Authentication errors indicate invalid or expired API tokens; reconfigure credentials.
    • HTTP 400 errors often mean invalid query parameters; verify property values.
    • HTTP 500 errors suggest server-side issues; retry after some time or contact support.

Links and References

Discussion