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 data related to various CRM resources. Specifically, for the "Proposal" resource with the "Get" operation, it fetches detailed information about a single proposal identified by its unique ID. This is useful in scenarios where you need to access specific proposal details within an automated workflow, such as generating reports, updating records, or triggering follow-up actions based on proposal data.
Practical examples include:
- Automatically retrieving proposal details when a new lead reaches a certain stage.
- Fetching proposal information to populate documents or emails.
- Integrating proposal data into dashboards or other business tools.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Proposal to retrieve. This string value specifies which proposal's details will be fetched from the Cloodo CRM system. |
Output
The node outputs JSON data representing the detailed information of the requested Proposal. The structure typically includes fields such as proposal ID, client information, status, amounts, dates, and any other metadata associated with the proposal in the Cloodo CRM.
If the node supports binary data output (not indicated explicitly here), it would generally represent attachments or files related to the proposal, but this is not evident from the provided code.
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
- Missing or invalid ID: If the ID property is empty or incorrect, the node will fail to retrieve the proposal. Ensure the ID is valid and corresponds to an existing proposal.
- Authentication errors: If the API key or token is missing, expired, or invalid, the node will return authorization errors. Verify that the credential is correctly set up in n8n.
- Network issues: Connectivity problems to the Cloodo API endpoint can cause timeouts or failures. Check network settings and firewall rules.
- API changes: If the Cloodo API changes its endpoints or data schema, the node might stop working correctly until updated.
Links and References
- Cloodo CRM API Documentation (Assumed base URL; check official docs for full API reference)
- n8n documentation on creating custom nodes