Actions17
Overview
This node integrates with the HighLevel API to update an existing Opportunity record. It allows users to modify various fields of an opportunity such as its assigned user, monetary value, name, pipeline, stage, and status. This is useful in CRM workflows where opportunity details need to be programmatically updated based on external triggers or automation logic.
Typical use cases include:
- Automatically updating the status of an opportunity when a deal progresses.
- Changing the assigned sales representative based on workload balancing.
- Adjusting the monetary value after receiving new information.
- Moving opportunities between pipelines or stages as part of a sales process automation.
Properties
| Name | Meaning |
|---|---|
| Opportunity ID | The unique identifier of the opportunity to update. This is required and cannot be used to change pipeline ID. |
| Update Fields | A collection of fields to update on the opportunity. These include: |
| - Assigned To | Select a user from the list or specify a user ID via expression to assign the opportunity to. |
| - Monetary Value | Numeric value representing the monetary worth of the opportunity. |
| - Name | The name/title of the opportunity (e.g., "John Deo"). |
| - Pipeline Name or ID | Choose a pipeline by name or ID to move the opportunity into a different sales pipeline. |
| - Stage Name or ID | Choose a stage within the selected pipeline by name or ID to update the opportunity's current stage. |
| - Status | The current status of the opportunity. Options are: Open, Won, Lost, Abandoned. |
Output
The node outputs JSON data representing the updated opportunity object returned from the HighLevel API. This typically includes all the opportunity's properties after the update operation, reflecting the new state.
If the node supports binary data output (not indicated here), it would represent any file attachments or related binary content associated with the opportunity.
Dependencies
- Requires an API authentication token configured in n8n credentials for the HighLevel API.
- Uses the HighLevel API base URL
https://services.leadconnectorhq.com. - Relies on helper methods to load options dynamically for users, pipelines, and pipeline stages.
- Pagination support is included for listing operations but not directly relevant for this update operation.
Troubleshooting
- Missing or invalid Opportunity ID: The update will fail if the provided Opportunity ID does not exist or is malformed. Ensure the ID is correct and corresponds to an existing opportunity.
- Pipeline ID immutability: The node hints that the pipeline ID cannot be updated directly through the Opportunity ID field. Instead, use the dedicated pipeline field to change pipelines.
- Invalid field values: Providing unsupported values for fields like status or assigned user may cause errors. Use the dropdowns or valid IDs.
- Authentication errors: If the API key or OAuth token is missing or expired, requests will fail. Verify credential configuration.
- Dependency loading issues: Dynamic option loading depends on other selections (e.g., pipeline must be selected before stages). Make sure dependencies are correctly set.
Links and References
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.