One original agency and sub-account remain bound. All native opportunity statuses are included; dates do not reconstruct historical stage changes. Contact identities, opportunity names, notes, appointments and monetary values are excluded.
This integration reads HighLevel data for reports and analysis. Source write actions are not available in Datapipe.
Use your reports in a sheet, a warehouse or a connected assistant, according to your plan and setup.
Examples for your team
Illustrative workflows using the supported capabilities. Connect your own account to work with your data.
Read & report
Review current pipeline outcomes
Keep native open, won, lost and abandoned statuses beside opportunity and stage IDs. A won state does not establish collected revenue.
Read & report
Keep the client scope visible
Refresh current pipeline configuration and sub-account identity together. Another client sub-account uses a separate project connection.
Reports you can build
3 reporting datasets with their own fields. Choose a dataset in the app, then select the columns you need.
See included datasets and what they report
Current sub-account opportunities
One current opportunity in the connected sub-account, across all native statuses. Report dates do not reconstruct pipeline history or filter creation dates. Native status and source are not verified conversions or revenue. Contact details, opportunity names, notes, tasks, appointments, custom fields and monetary values are excluded. No records are changed.
Current sub-account pipelines
One current pipeline in the connected sub-account. Report dates do not reconstruct earlier pipeline configuration. Native display settings and sort keys are retained; this is not a historical funnel or stage conversion report. Stage definitions and their untyped nested content are excluded.
Connected sub-account
Current agency and sub-account identity with native country and time zone. Report dates do not reconstruct identity history. One sub-account remains bound to the original agency across every report and credential replacement.
One original agency and sub-account remain bound. Provider access and request limits apply. Reports describe current state across all native statuses, independent of report dates. Contacts, opportunity names, notes, tasks, appointments, custom fields and monetary values are excluded. Native won status is not verified collected revenue.
Metrics and dimensions
28 report fields across 3 datasets.
Browse the documented fields below. In the app, choose your project connection to load its field list. Availability depends on API permissions, report type, and compatible field combinations. Property-specific custom fields appear after connecting.
No fields match. Try another search or choose All.
Create a project and choose HighLevel in Connections.
Prefer Sign in when configured, or create a dedicated sub-account private integration with only location and opportunity read permissions.
Pick where it goes. Reports describe current state; changing report dates does not reconstruct historical pipeline movement.
Sample report
Sample
Opportunity ID
Pipeline ID
Pipeline stage ID
Native opportunity status
Opportunity source
Created at
Updated at
Last status change at
1,240
1,240
Lead
Paid
1,240
1,240
Oct 27
Paid
640
640
Proposal
Pending
640
640
Oct 28
Pending
210
210
Won
Refunded
210
210
Oct 29
Refunded
Sample numbers, so you can see the shape. Your report uses your accounts.
Current opportunities, pipeline configuration and identity from one agency-owned sub-account. Native opportunity statuses and source values are retained. Report dates do not reconstruct historical pipeline movement. Contacts, opportunity names, notes, tasks, appointments, custom fields and monetary values are excluded. No source changes or webhooks.
Questions
Free to start. Paid plans add more connections and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 connections.
No. Name a project, add a connection, then choose a report and destination.
This integration is read-only in Datapipe. You can read the supported reports, share them with reporting destinations and ask a connected assistant about the available data. Sending report output to a destination does not grant editing access to this source. Read-only locations.readonly and opportunities.readonly access using a sub-account Private Integration Token, or provider sign-in after Datapipe app registration. Credentials stay bound to one original agency/sub-account. Agencies use their own eligible HighLevel account; Datapipe does not supply a shared subscription.
This page lists 28 report fields across 3 datasets. You pick the columns when you build the report.
Current opportunities, pipeline configuration and identity from one agency-owned sub-account. Native opportunity statuses and source values are retained. Report dates do not reconstruct historical pipeline movement. Contacts, opportunity names, notes, tasks, appointments, custom fields and monetary values are excluded. No source changes or webhooks. Account permissions and the records available from the provider determine which rows can be read.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.