Actions26
Overview
The "Find or Create" operation for the Opportunity resource in this node interacts with the GoHighLevel V2 API to either find an existing opportunity based on specified criteria or create a new one if no matching opportunity is found. This operation is useful in scenarios where you want to ensure that an opportunity exists without creating duplicates, such as syncing CRM data, automating sales pipelines, or integrating lead management workflows.
Practical examples include:
- Automatically creating an opportunity when a new contact expresses interest, but only if an opportunity does not already exist.
- Searching for an opportunity by contact ID and updating it if found, or creating a new one otherwise.
- Integrating with marketing automation tools to track potential deals dynamically.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The identifier of the contact associated with the opportunity. Used to link the opportunity to a specific contact. |
| Additional Fields | A collection of optional fields to further define or customize the opportunity: |
| - Contact ID | (Optional) Another way to specify the contact ID linked to the opportunity. |
| - Custom Fields | Allows adding multiple custom fields by specifying their name or ID and corresponding values. Useful for storing additional metadata or custom attributes related to the opportunity. |
| - Monetary Value | The monetary value assigned to the opportunity, representing its potential revenue or worth. |
| - Name | The name/title of the opportunity, typically describing the deal or sales opportunity. |
| - Pipeline ID | The identifier of the sales pipeline to which this opportunity belongs. Helps organize opportunities within different sales processes or stages. |
| - Pipeline Stage ID | The identifier of the specific stage within the pipeline where the opportunity currently resides. Useful for tracking progress through the sales funnel. |
Output
The node outputs JSON data representing the opportunity object(s) returned from the GoHighLevel API after performing the find or create operation. The structure includes all standard and custom fields of the opportunity, reflecting its current state in the system.
If multiple opportunities are returned (e.g., from a search), the output will be an array of JSON objects, each representing one opportunity.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the GoHighLevel V2 API via OAuth2 authentication.
- The node depends on the GoHighLevelManager utility to fetch custom fields dynamically.
- Proper API credentials must be configured in n8n to authenticate requests.
- The node uses internal helper functions to handle operations per resource type.
Troubleshooting
Common Issues:
- Missing or invalid API credentials can cause authentication failures.
- Providing incorrect or non-existent Contact IDs may result in no matches found or errors.
- Custom field IDs must be valid; otherwise, the API may reject the request.
- Network connectivity issues can prevent communication with the GoHighLevel API.
Error Messages:
"The resource \"opportunity\" is not known!"— indicates an unsupported resource was selected; ensure "Opportunity" is chosen.- API error messages related to invalid fields or permissions should be checked against the GoHighLevel API documentation.
- If the node throws errors about missing parameters, verify that required fields like Contact ID or Name are provided when necessary.
Resolution Tips:
- Double-check API credentials and permissions.
- Validate all input fields, especially custom fields and IDs.
- Use the node's "Continue On Fail" option to handle errors gracefully during batch processing.