Cloodo CRM icon

Cloodo CRM

Get data from Cloodo API

Actions62

Overview

This node interacts with the Cloodo CRM API to retrieve multiple engagement records associated with a specific project. It is designed to fetch paginated lists of engagements filtered by project ID, optionally constrained by date ranges and sorted order.

Common scenarios where this node is beneficial include:

  • Extracting all customer or client engagements related to a particular project for reporting or analysis.
  • Synchronizing engagement data from Cloodo CRM into other systems based on project context.
  • Monitoring project activity by reviewing engagement history within specified time frames.

For example, a user might want to get the first 25 engagements for project "12345" sorted descending by date, only including engagements from January 1, 2024, to March 31, 2024.

Properties

Name Meaning
Project_id The unique identifier of the project whose engagements are to be retrieved.
Page The page number of results to fetch (pagination).
Additional Fields Optional parameters to refine the query:
- Limit: Number of engagements per page (10, 25, or 50).
- Sort: Order of results by date, either "desc" (descending) or "asc" (ascending).
- From Date: Start date filter for engagements (ISO string).
- To Date: End date filter for engagements (ISO string).

Output

The node outputs JSON data representing an array of engagement objects related to the specified project. Each engagement object typically contains details such as engagement identifiers, timestamps, status, and other metadata as provided by the Cloodo CRM API.

If binary data were involved (e.g., attachments), it would be included in a separate binary property, but this operation focuses on JSON engagement records only.

Dependencies

  • Requires an active connection to the Cloodo CRM API endpoint at https://erp-amz.cloodo.com/v4/.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The node depends on proper network access to the Cloodo CRM service.

Troubleshooting

  • Invalid Project ID: If the project ID is incorrect or does not exist, the API may return an empty list or an error. Verify the project ID before running.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n credentials.
  • Pagination Issues: Requesting pages beyond available data returns empty results. Adjust the page number accordingly.
  • Date Format Errors: The "From Date" and "To Date" fields must be valid date strings; otherwise, the API may reject the request.
  • Rate Limits: Excessive requests may trigger rate limiting by the API. Implement delays or reduce request frequency if needed.

Links and References

Discussion