EspoCRM
Interact with EspoCRM API to manage accounts, contacts, leads, and opportunities. Create, read, update and delete CRM records.
Actions21
Overview
This node allows you to create a new Opportunity record in a CRM system. It is useful for automating sales processes by programmatically adding potential deals or sales opportunities into your CRM database. For example, when a lead qualifies through a marketing campaign, this node can automatically create an opportunity with relevant details such as the name, associated account and contact, sales stage, expected close date, and estimated amount.
Properties
| Name | Meaning |
|---|---|
| Name | The name 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 stage of the opportunity in the sales pipeline. Options: |
| - Prospecting | |
| - Qualification | |
| - Needs Analysis | |
| - Value Proposition | |
| - Id. Decision Makers | |
| - Perception Analysis | |
| - Proposal/Price Quote | |
| - Negotiation/Review | |
| - Closed Won | |
| - Closed Lost | |
| Amount | The monetary value of the opportunity (minimum 0). |
| Probability | The likelihood of closing the deal, expressed as a percentage from 0 to 100. |
| Close Date | The expected date when the opportunity will be closed. |
| Lead Source | The origin of the opportunity. Options: |
| - Call | |
| - Existing Customer | |
| - Partner | |
| - Public Relations | |
| - Web Site | |
| - Campaign | |
| - Other |
Output
The node outputs JSON data representing the newly created Opportunity record. This typically includes all fields sent during creation along with any additional metadata or identifiers assigned by the CRM system. There is no indication that binary data is output by this node.
Dependencies
- Requires connection to a compatible CRM system supporting Opportunity records.
- Needs appropriate API credentials or authentication tokens configured in n8n to authorize creation requests.
- The node depends on external modules for descriptions and operations, but these are bundled internally.
Troubleshooting
- Missing Required Fields: If the "Name" property is not provided, the node will likely throw an error since it is required.
- Invalid Field Values: Providing invalid values for fields like "Probability" (outside 0-100) or negative "Amount" may cause errors.
- Authentication Errors: Failure to provide valid API credentials or tokens will result in authorization errors.
- Network Issues: Connectivity problems with the CRM API endpoint can cause timeouts or request failures.
- To resolve errors, verify all required properties are set correctly, ensure valid credentials are configured, and check network connectivity.
Links and References
- Refer to your CRM system's API documentation for detailed information about Opportunity object fields and creation endpoints.
- n8n documentation on creating custom nodes and managing credentials may help with setup and troubleshooting.