Actions16
Overview
This n8n node allows you to create a new Opportunity in the HighLevel CRM platform. It is designed for automating sales pipeline management by programmatically adding opportunities (deals) associated with contacts, stages, and pipelines. This is useful for sales teams who want to automate lead tracking, deal progression, or integrate HighLevel with other tools.
Example scenarios:
- Automatically create an opportunity when a new lead is captured from a web form.
- Add deals to specific pipelines/stages based on user actions in another system.
- Integrate with marketing automation to track sales progress.
Properties
| Name | Type | Meaning |
|---|---|---|
| Pipeline ID | options | Select or specify the pipeline where the opportunity will be created. |
| Stage ID | options | (Required) Select or specify the stage within the chosen pipeline for the new opportunity. |
| Contact Identifier | string | (Required) Email, phone, or contact ID to associate the opportunity with a contact. |
| Title | string | (Required) The title or name of the opportunity/deal. |
| Status | options | (Required) The status of the opportunity (Open, Won, Lost, Abandoned). |
| Additional Fields | collection | Optional extra fields: Assigned To, Company Name, Monetary Value, Name, Tags. |
Additional Fields (collection):
- Assigned To: options — Assign the opportunity to a user.
- Company Name: string — Name of the company related to the opportunity.
- Monetary Value: number — Estimated value of the opportunity.
- Name: string — An additional name field for the opportunity.
- Tags: string[] — Tags to categorize the opportunity.
Output
The node returns a JSON object representing the newly created opportunity. The structure typically includes:
{
"id": "string",
"title": "string",
"status": "string",
"stageId": "string",
"pipelineId": "string",
"contactIdentifier": "string",
"assignedTo": "string",
"companyName": "string",
"monetaryValue": "number",
"tags": ["string", "..."],
...
}
Note: The actual output may include additional fields returned by the HighLevel API.
Dependencies
- HighLevel API: Requires access to the HighLevel CRM API.
- API Key: You must configure the
highLevelApicredential in n8n with your HighLevel API key. - Environment: No special environment variables are required beyond standard n8n setup.
Troubleshooting
Common issues:
- Missing Required Fields: If required fields like Stage ID, Contact Identifier, Title, or Status are missing, the node will throw validation errors.
- Invalid IDs: Supplying incorrect Pipeline or Stage IDs will result in API errors such as "Not Found" or "Invalid ID".
- Authentication Errors: Incorrect or expired API keys will cause authentication failures.
Error messages and resolutions:
"Missing required property": Ensure all required fields are filled."Unauthorized": Check that your HighLevel API credentials are correct and active."Resource not found": Verify that the provided Pipeline/Stage/Contact IDs exist in your HighLevel account.