Actions17
Overview
This node integrates with a CRM-like service to create new sales opportunities. It allows users to specify key details about an opportunity such as the pipeline it belongs to, the contact associated with it, its name, status, and other optional fields like assigned user, company name, monetary value, tags, and stage within the pipeline.
Common scenarios for this node include automating lead management workflows, syncing opportunities from external sources, or programmatically creating sales opportunities based on triggers in other systems (e.g., form submissions, email interactions).
For example, when a new lead fills out a web form, this node can automatically create an opportunity linked to that lead's contact record, assign it to a sales rep, and set its initial status and pipeline stage.
Properties
| Name | Meaning |
|---|---|
| Pipeline Name or ID | Select the sales pipeline where the opportunity will be created. You can choose from a list of pipelines or specify an ID using an expression. |
| Contact Email or ID | The contact associated with the opportunity. Only one opportunity per contact is allowed. Choose from existing contacts or specify an ID via expression. This field is required. |
| Name | The name/title of the opportunity. This is a required string field. |
| Status | The current status of the opportunity. Options are: Open, Won, Lost, Abandoned. Default is Open. |
| Additional Fields | A collection of optional fields to provide more details about the opportunity: |
| - Assigned To | Assign the opportunity to a specific user. Choose from a list or specify an ID via expression. |
| - Company Name | The company name related to the opportunity. |
| - Monetary Value | The estimated monetary value of the opportunity. |
| - Tags | Comma-separated list of tags to categorize the opportunity. Can also be set as an array of strings via expression. |
| - Stage Name or ID | The stage within the selected pipeline. Options depend on the chosen pipeline and can be selected from a list or specified by ID using an expression. |
Output
The node outputs JSON data representing the newly created opportunity object as returned by the API. This typically includes all the fields sent during creation along with additional metadata such as unique identifiers, timestamps, and possibly related resource links.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the opportunity, but this node appears focused solely on JSON data.
Dependencies
- Requires an API authentication token configured in n8n credentials to access the external CRM service.
- Uses several dynamic option loading methods to populate dropdowns for pipelines, contacts, users, and pipeline stages by querying the API.
- The base URL for API requests is
https://services.leadconnectorhq.com. - Requests include headers specifying JSON content type and a version header.
Troubleshooting
- Error: Missing required fields — Ensure that mandatory properties like Contact and Name are provided; otherwise, the API will reject the request.
- Error: Duplicate opportunity for contact — Since only one opportunity per contact is allowed, attempting to create another may cause an error. Verify if an opportunity already exists for the contact before creating a new one.
- Error: Invalid pipeline or stage ID — If you specify IDs manually, ensure they exist and correspond correctly; otherwise, the API may return validation errors.
- Authentication failures — Check that the API authentication token is valid and has not expired.
- Empty dropdown options — If dynamic option loading fails (e.g., no pipelines or contacts appear), verify network connectivity and API permissions.
Links and References
- n8n Expressions Documentation
- HighLevel API documentation (not publicly linked here, refer to your service provider's docs)