Actions17
Overview
The node integrates with the HighLevel API to retrieve multiple Opportunity records based on specified filters and pagination options. It is useful for workflows that need to fetch a list of sales opportunities, such as generating reports, syncing data with other systems, or triggering actions based on opportunity statuses.
For example, you can use this node to:
- Retrieve all open opportunities assigned to a specific user.
- Fetch opportunities within a certain pipeline stage or date range.
- Limit results to a maximum number for batch processing.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching opportunity records or limit the number of results. |
| Limit | Maximum number of opportunity records to return when "Return All" is false. Minimum value is 1. |
| Filters | Collection of optional filters to narrow down the opportunities returned: |
| - Assigned To | Filter by the user assigned to the opportunity. Select from a list or specify an ID via expression. |
| - Campaign ID | Filter by campaign identifier (string). |
| - End Date | Filter opportunities ending before this date/time. |
| - Pipeline Name or ID | Filter by pipeline. Choose from a list or specify an ID via expression. |
| - Stage Name or ID | Filter by pipeline stage. Depends on selected pipeline. Choose from a list or specify an ID via expression. |
| - Start Date | Filter opportunities starting after this date/time. |
| - Status | Filter by opportunity status. Options are: Open, Won, Lost, Abandoned. Default is Open. |
| - Query | Text search query applied to fields: Name, Phone, Email, Tags, and Company Name. |
Output
The node outputs JSON data containing an array of opportunity objects matching the filter criteria. Each object represents an opportunity with its associated properties as returned by the HighLevel API.
If "Return All" is enabled, the output includes all matching opportunities; otherwise, it contains up to the specified limit.
No binary data output is indicated in the source code.
Dependencies
- Requires an OAuth2 API credential configured for the HighLevel service.
- The node uses the base URL
https://services.leadconnectorhq.comand expects API version2021-07-28. - Pagination support is implemented via a helper function integrated into the request operations.
Troubleshooting
- Authentication errors: Ensure the OAuth2 credentials are correctly set up and have valid tokens.
- Empty results: Verify filter values, especially IDs for users, pipelines, and stages, are correct and exist in your HighLevel account.
- Invalid limit values: The limit must be at least 1; setting lower values may cause errors.
- Dependency loading issues: The node relies on dynamic loading of options like users, pipelines, and stages. If these fail to load, check API connectivity and permissions.
- Date filter format: Dates should be provided in ISO 8601 format; incorrect formats might result in no matches or errors.