EspoCRM
Interact with EspoCRM API to manage accounts, contacts, leads, and opportunities. Create, read, update and delete CRM records.
Actions21
Overview
The node updates an existing Opportunity record in a CRM system. It allows users to modify various fields of an opportunity such as its name, associated account and contact, sales stage, amount, probability of closing, expected close date, and lead source. This is useful for keeping opportunity data current during the sales process, reflecting changes like progressing stages, updated amounts, or new contacts.
Practical examples:
- Updating the stage of an opportunity from "Prospecting" to "Negotiation/Review" after initial discussions.
- Changing the expected close date based on new information from the client.
- Adjusting the probability percentage as the deal becomes more or less likely to close.
Properties
| Name | Meaning |
|---|---|
| Opportunity ID | The unique identifier of the opportunity to update (required). |
| Name | The name/title of the opportunity (required). |
| Account ID | The identifier of the account associated with this opportunity. |
| Contact ID | The identifier of the contact person related to this opportunity. |
| Stage | The current sales stage of the opportunity. Options: Prospecting, Qualification, Needs Analysis, Value Proposition, Id. Decision Makers, Perception Analysis, Proposal/Price Quote, Negotiation/Review, Closed Won, Closed Lost. Default is Prospecting. |
| Amount | The monetary value of the opportunity (minimum 0). |
| Probability | The likelihood of closing the opportunity expressed as a percentage (0-100). |
| Close Date | The expected date when the opportunity will close. |
| Lead Source | The origin of the opportunity. Options: Call, Email, Existing Customer, Partner, Public Relations, Web Site, Campaign, Other. Default is Web Site. |
Output
The node outputs JSON data representing the updated opportunity record. This typically includes all the fields that were updated along with any additional metadata returned by the CRM system. There is no indication that binary data is output by this node.
Dependencies
- Requires connection to the CRM system's API where opportunities are managed.
- Needs appropriate API authentication credentials configured in n8n to authorize update operations.
- The node depends on internal operation execution logic imported from bundled dependencies but does not specify external libraries beyond that.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Opportunity ID will result in errors as the system cannot find the record to update.
- Missing required fields like Opportunity ID or Name will cause validation failures.
- Incorrect data types (e.g., negative amount or probability outside 0-100) may be rejected.
- Authentication failures if API credentials are missing or incorrect.
Error messages and resolutions:
- "Opportunity not found": Verify the Opportunity ID is correct and exists in the CRM.
- "Missing required field" or "Validation error": Ensure all mandatory properties are provided and valid.
- "Authentication failed": Check API credentials and permissions.
- "Invalid data format": Confirm numeric fields are within allowed ranges and dates are properly formatted.
Links and References
- Refer to your CRM system’s API documentation for details on updating opportunity records.
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/integrations/creating-nodes/
- General best practices for managing sales opportunities in CRM systems.