Actions62
- Client Actions
- ClientDetail Actions
- Engagement Actions
- Estimate Actions
- Lead Actions
- Lead Agent Actions
- Lead Category Actions
- Lead Source Actions
- Lead Status Actions
- Proposal Actions
- Project Actions
- Task Actions
- Note Actions
Overview
The node interacts with the "Estimate" resource of the Cloodo CRM API, specifically supporting the operation to retrieve multiple estimates ("Get Many Estimates"). It fetches a paginated list of estimate records, optionally filtered by status and date range. This is useful for users who want to analyze or process batches of estimates from their CRM system, such as generating reports, syncing data with other tools, or monitoring estimate statuses over time.
Practical examples:
- Retrieve all estimates created within a specific date range to review recent sales opportunities.
- Filter estimates by status (e.g., approved, pending) to focus on relevant subsets.
- Paginate through large sets of estimates to export them in manageable chunks.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of results to retrieve (pagination). Defaults to 1. |
| Additional Fields | Optional filters to refine the query: |
| - Status ID | Filter estimates by a specific status identifier. |
| - From Date | Start date to filter estimates created on or after this date (format expected by API). |
| - To Date | End date to filter estimates created on or before this date (format expected by API). |
Output
The node outputs an array of JSON objects representing estimates retrieved from the Cloodo CRM API. Each object corresponds to one estimate record and includes fields as provided by the API, such as estimate details, status, dates, amounts, and related metadata.
If the API supports binary data for estimates (not indicated here), it would be included accordingly, but based on the static code and properties, output is JSON-only.
Dependencies
- Requires an active connection to the Cloodo CRM API via an API key credential configured in n8n.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/. - Proper permissions on the API key to access estimate data are necessary.
Troubleshooting
- Empty Results: If no estimates are returned, verify that the page number and filters (status ID, date range) are correct and that matching data exists.
- Invalid Date Format: Ensure that "From Date" and "To Date" values conform to the expected date format required by the API (likely ISO 8601).
- Authentication Errors: Confirm that the API key credential is valid and has not expired.
- Pagination Issues: If too many results are requested at once or page numbers exceed available pages, the API may return errors or empty arrays.
- API Rate Limits: Excessive requests might trigger rate limiting; implement delays or retries if needed.
Links and References
- Cloodo CRM API Documentation (base URL used in node)
- General REST API pagination and filtering best practices (varies by API provider)