Actions17
Overview
This node integrates with the HighLevel API to perform various operations on different resources such as Contacts, Opportunities, Tasks, and Calendars. Specifically, for the Opportunity - Get operation, it retrieves detailed information about a single opportunity by its unique identifier. This is useful in scenarios where you want to fetch up-to-date data about a specific sales opportunity, for example, to display its status, value, or related details within an automation workflow.
Practical examples include:
- Fetching opportunity details to update a CRM dashboard.
- Using opportunity data to trigger follow-up actions based on its current stage.
- Integrating opportunity information into reporting or notification systems.
Properties
| Name | Meaning |
|---|---|
| Opportunity ID | The unique identifier of the opportunity to retrieve. This is required to specify which opportunity's details to fetch. |
Output
The node outputs JSON data representing the full details of the requested opportunity. This typically includes fields such as the opportunity's name, status, pipeline stage, associated contacts, monetary values, dates, and other metadata as provided by the HighLevel API.
If the node supports binary data output (not indicated here), it would be summarized as containing any files or attachments related to the opportunity, but this is not evident from the static code.
Dependencies
- Requires an API authentication token credential configured in n8n to access the HighLevel API.
- The base URL for API requests is
https://services.leadconnectorhq.com. - Requests use JSON format with headers specifying content type and API version.
- Pagination support is included for list operations but not relevant for the single "Get" operation.
Troubleshooting
Common issues:
- Invalid or missing Opportunity ID will cause the request to fail.
- Authentication errors if the API token is invalid or expired.
- Network connectivity problems preventing access to the HighLevel API endpoint.
Error messages:
- Unauthorized or 401 errors indicate issues with the API credentials; re-authenticate or update the token.
- 404 Not Found may occur if the specified Opportunity ID does not exist.
- 400 Bad Request can happen if the Opportunity ID format is incorrect.
Resolving these usually involves verifying the input Opportunity ID, ensuring valid API credentials are set up, and checking network connectivity.
Links and References
- HighLevel API Documentation (for detailed API endpoints and data structures)
- n8n documentation on creating custom nodes