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 integrates with the Cloodo CRM API to retrieve multiple lead records. It is designed to fetch a paginated list of leads, optionally filtered by various criteria such as search terms, status, date ranges, and assigned agent. This node is useful in scenarios where users want to automate lead management workflows, synchronize leads with other systems, or analyze lead data programmatically.
Practical examples:
- Fetching all leads created within a specific date range for reporting.
- Retrieving leads assigned to a particular sales agent to trigger follow-up actions.
- Searching leads by keywords to filter relevant prospects for marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of the lead list to retrieve (pagination). Defaults to 1. |
| Additional Fields | Optional filters to refine the lead query: |
| - Search | A search string to filter leads by matching text fields. |
| - Status ID | Filter leads by their status identifier. |
| - From Date | Start date to filter leads created from this date (format expected by API). |
| - To Date | End date to filter leads created up to this date (format expected by API). |
| - Agent ID | Filter leads assigned to a specific agent by their identifier. |
Output
The node outputs an array of lead objects in the json field of the output data. Each object represents a lead record retrieved from the Cloodo CRM system, containing properties such as lead details, status, source, assigned agent, creation dates, and other metadata as provided by the API.
If the API supports binary data related to leads (e.g., attachments), the node would include it accordingly, but based on the provided code and properties, the primary output is JSON-formatted lead data.
Dependencies
- Requires an active connection to the Cloodo CRM API endpoint at
https://erp-amz.cloodo.com/v4/. - Needs an API authentication token or key configured in the node credentials to authorize requests.
- The node depends on the Cloodo CRM service being available and responsive.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect date formats in "From Date" or "To Date" may result in API errors or empty results.
- Requesting pages beyond the available data range may return empty arrays.
- Filtering by non-existent status IDs or agent IDs will yield no results.
Error messages and resolutions:
- Authentication failed: Verify that the API key or token is correctly set in the node credentials.
- Invalid query parameter: Check the format and validity of filter values like dates and IDs.
- Network errors: Ensure network connectivity and that the Cloodo CRM API endpoint is reachable.
- Empty response: Confirm that the filters applied match existing leads; try broadening search criteria.
Links and References
- Cloodo CRM API Documentation (Assumed base URL, check official docs for detailed API reference)
- n8n Documentation on Creating Custom Nodes
- General REST API Pagination Concepts: https://restfulapi.net/pagination-in-rest-api/
Note: The summary is based solely on static analysis of the provided source code and property definitions without runtime execution.