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
This node integrates with the Cloodo CRM system to retrieve data related to lead sources. Specifically, the "Get Many Leads Source" operation fetches multiple lead source records from the Cloodo API. This is useful for scenarios where you want to list or analyze all available lead sources in your CRM, such as for reporting, filtering leads by their origin, or syncing lead source data with other systems.
Practical examples:
- Fetching all lead sources to populate a dropdown menu in a form.
- Synchronizing lead source data into another marketing or sales platform.
- Generating reports on which lead sources bring the most leads.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional extra parameters to refine the request. Currently supports: |
| - Search | A string to filter lead sources by name or other searchable fields (query parameter). |
Output
The node outputs JSON data representing an array of lead source objects retrieved from the Cloodo API. Each object typically contains details about a lead source, such as its identifier, name, and possibly other metadata defined by the API.
If binary data were involved (not indicated here), it would represent files or attachments related to lead sources, but this node focuses on 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.
- The base URL for API requests is
https://erp-amz.cloodo.com/v4/.
Troubleshooting
Common issues:
- Authentication failures due to missing or invalid API credentials.
- Network connectivity problems preventing access to the Cloodo API endpoint.
- Invalid search query syntax causing empty or error responses.
Error messages:
- 401 Unauthorized: Check that the API key credential is correctly set up and has proper permissions.
- 404 Not Found: Verify that the resource and operation are correctly selected.
- 400 Bad Request: Ensure that any search strings or additional fields conform to expected formats.
Resolving these usually involves verifying credentials, checking network access, and validating input parameters.
Links and References
- Cloodo CRM API Documentation (assumed base URL; consult official docs for detailed API specs)