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 API to retrieve project proposal data. It is designed to fetch proposals related to projects managed within the Cloodo platform. Typical use cases include automating the retrieval of project proposals for reporting, analysis, or further processing in workflows such as sending proposal details to clients, updating internal databases, or triggering follow-up actions based on proposal status.
For example, a user might configure this node to get all proposals for a specific project within a date range or limit the number of proposals retrieved per request to manage large datasets efficiently.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the project for which to retrieve proposals. |
| Page | The page number of results to retrieve when fetching multiple proposals (pagination). |
| Additional Fields | Optional parameters to refine the query: |
| - Limit | Number of proposals to return per page. Options: 10, 25, 50. |
| - From Date | Start date filter to retrieve proposals created or modified from this date onwards (format as string). |
| - To Date | End date filter to retrieve proposals up to this date (format as string). |
Output
The node outputs JSON data representing the project proposals retrieved from the Cloodo API. Each item in the output corresponds to a single project proposal and includes fields such as proposal details, associated project information, dates, amounts, and statuses as provided by the API.
If the API supports binary data for proposals (e.g., attached documents), the node would handle it accordingly, but based on the static code and properties, the primary output is structured JSON data about proposals.
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/. - Proper network access to the Cloodo API endpoint must be ensured.
Troubleshooting
- Invalid or missing ID: If the project ID is not provided or incorrect, the API may return errors or empty results. Ensure the correct project ID is entered.
- Pagination issues: Requesting pages beyond available data will result in empty responses. Adjust the "Page" property accordingly.
- Date format errors: The "From Date" and "To Date" fields expect properly formatted date strings. Incorrect formats may cause API errors.
- API authentication failures: Verify that the API key or token credential is correctly set up and has sufficient permissions.
- Rate limiting or connectivity problems: Network issues or API rate limits can cause request failures. Check connectivity and API usage quotas.
Links and References
- Cloodo CRM API Documentation (Assumed typical location; replace with actual if known)
- n8n Documentation on HTTP Request Node for understanding API integrations.
- General best practices for API Pagination and date filtering.