Actions26
Overview
This node integrates with the GoHighLevel V2 API to manage "Opportunity" resources, specifically supporting the "Update or Create" operation. It allows users to either update an existing opportunity or create a new one if it does not exist. This is useful in sales and CRM workflows where opportunities need to be dynamically maintained based on incoming data, such as updating pipeline stages, monetary values, or custom fields.
Practical examples include:
- Automatically creating a new sales opportunity when a lead reaches a certain stage.
- Updating an existing opportunity’s monetary value or pipeline stage based on recent customer interactions.
- Syncing opportunity data from external systems into GoHighLevel.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The identifier of the contact associated with the opportunity. |
| Additional Fields | A collection of optional fields to further define or update the opportunity: |
| - Contact ID | (Optional) Contact ID to associate with the opportunity. |
| - Custom Fields | Multiple custom fields can be added, each with a field name or ID and its corresponding value. |
| - Monetary Value | The monetary value assigned to the opportunity. |
| - Name | The name/title of the opportunity. |
| - Pipeline ID | The ID of the sales pipeline this opportunity belongs to. |
| - Pipeline Stage ID | The ID of the current stage within the pipeline for this opportunity. |
Output
The node outputs JSON objects representing the updated or newly created opportunity records as returned by the GoHighLevel API. Each output item contains the full details of the opportunity after the operation, including any fields set or modified.
If multiple items are processed, the output is an array of such JSON objects.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the GoHighLevel V2 API via OAuth2 authentication.
- The node depends on the GoHighLevelManager utility internally to fetch custom fields and perform API operations.
- Proper API credentials must be configured in n8n to authenticate requests.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing invalid IDs for pipeline, pipeline stage, or contact may result in errors from the API.
- Custom field names or IDs must match those defined in GoHighLevel; otherwise, updates may silently fail or error out.
Error Messages:
"The resource \"opportunity\" is not known!"— indicates an unsupported resource was selected; ensure "Opportunity" is chosen.- API errors related to invalid parameters typically indicate incorrect field values or missing required fields.
Resolution Tips:
- Verify all IDs (contact, pipeline, stage) exist in your GoHighLevel account.
- Use the node’s load options to select valid custom fields to avoid typos.
- Enable "Continue On Fail" to handle partial failures gracefully during batch processing.