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 system to update Proposal records. It allows users to modify various fields of an existing Proposal by specifying its unique ID and providing updated values for one or more properties. This is useful in scenarios where proposals need to be adjusted after creation, such as changing the status, updating financial details like totals and discounts, or assigning a different agent.
Practical examples include:
- Marking a proposal as "Accepted" or "Declined" based on client feedback.
- Updating the validity date or currency of a proposal.
- Adjusting subtotal, total, or discount amounts after negotiations.
- Changing the assigned sales agent responsible for the proposal.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Proposal to update. |
| Additional Fields | A collection of optional fields to update on the Proposal: |
| - Lead | Numeric ID referencing the associated lead. |
| - Valid Till | Date string indicating the expiration date of the proposal's validity. |
| - Sub Total | Numeric value representing the subtotal amount before taxes and discounts. |
| - Total | Numeric value representing the final total amount of the proposal. |
| - Currency | Numeric ID representing the currency used in the proposal. |
| - Discount | Numeric value indicating any discount applied to the proposal. |
| - Agent | String ID of the agent assigned to the proposal. |
| - Status | Status of the proposal; options include: Accepted, Analysing, Declined, Draft, Waiting. |
| - Calculate Tax | Specifies when tax calculation occurs relative to discount application; options are: After Discount, Before Discount. |
Output
The node outputs JSON data representing the updated Proposal record as returned by the Cloodo API. This typically includes all the Proposal's fields reflecting the new state after the update operation.
If the node supports binary data output (not indicated here), it would 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 endpoint at
https://erp-amz.cloodo.com/v4/. - Needs an API authentication token or key credential configured within n8n to authorize requests.
- The node depends on the Cloodo API being available and responsive.
Troubleshooting
Common Issues:
- Invalid or missing Proposal ID will cause the update to fail.
- Providing invalid field values (e.g., wrong data types or unsupported status IDs) may result in API errors.
- Network connectivity issues or incorrect API credentials will prevent successful updates.
Error Messages:
- "Proposal not found" indicates the specified ID does not exist; verify the ID.
- "Unauthorized" or "Authentication failed" suggests problems with API credentials.
- Validation errors from the API may indicate improper field formats or missing required fields.
To resolve these, ensure the Proposal ID is correct, input values conform to expected types and constraints, and that API credentials are valid and have sufficient permissions.
Links and References
- Cloodo CRM API Documentation (assumed base URL; consult official docs for detailed API reference)
- n8n documentation on creating custom nodes for further customization guidance