Cloodo CRM icon

Cloodo CRM

Get data from Cloodo API

Actions62

Overview

This node interacts with the "Proposal" resource of the Cloodo CRM API to retrieve multiple proposal records ("Get Many" operation). It is useful for scenarios where you need to fetch a list of proposals with various filtering, sorting, and pagination options. For example, a user might want to get all proposals related to a specific project or lead, filter by status, or limit the number of results per page.

Practical examples:

  • Fetching the first 10 proposals sorted in descending order by date.
  • Retrieving proposals filtered by a specific agent or ticket ID.
  • Getting proposals within a certain date range (fromDate to toDate).

Properties

Name Meaning
Page The page number of results to retrieve (pagination).
Limit Number of proposals to return per request. Options: 10, 25, 50.
ticketID Filter proposals by a specific ticket ID (number).
From Date Start date to filter proposals from (string, typically in date format).
To Date End date to filter proposals up to (string, typically in date format).
Sort Order of results by date or other criteria. Options: DESC (descending), ASC (ascending).
Filter by Lead ID Filter proposals associated with a specific lead ID (string).
Filter by Project ID Filter proposals associated with a specific project ID (string).
Filter by Ticket ID Filter proposals associated with a specific ticket ID (string).
Filter by Agent ID Filter proposals associated with a specific agent ID (string).
Filter by Status Filter proposals by their status. Options include Accepted, Analysing, Declined, Draft, Waiting.

Output

The node outputs JSON data containing an array of proposal objects matching the specified filters and pagination settings. Each proposal object includes details as provided by the Cloodo CRM API for proposals.

If binary data were involved (e.g., attachments), it would be included in the binary output field, but this operation focuses on retrieving JSON data only.

Dependencies

  • Requires an active connection to the Cloodo CRM API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • Base URL used: https://erp-amz.cloodo.com/v4/

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Incorrect filter values (e.g., invalid date formats) may result in empty responses or API errors.
    • Pagination parameters out of range could lead to no data returned.

  • Error messages:

    • Authentication failures: Check that the API key or token is correctly set up in n8n credentials.
    • Validation errors from the API: Verify that filter fields like dates and IDs are correctly formatted.
    • Network errors: Ensure connectivity to the Cloodo CRM API endpoint.

Links and References

Discussion