To authorize the Workflows API, generate a GHL API key with the surveys.readonly scope and configure it in your Humi connection settings. Use secure storage for credentials and test access with a quick data pull first.
In Humi, enable API access for the GHL connection and grant the necessary permissions. If using OAuth, keep client credentials secure and refresh tokens as needed. Ensure the user accounts involved have access to surveys data.
GET /surveys/ — fetches all surveys. GET /surveys/submissions — fetches submissions for those surveys. Additional endpoints exist in the API documentation, but only these are required for this page.
Trigger: A new or updated survey in Humi prompts a pull of survey data into GHL Workflows.
Actions: Create or update a survey record in Workflows and start analytics workflows.
GET /surveys/
survey_id, title, created_at, updated_at
Trigger: A new submission is added in Humi.
Actions: Push submission data into Workflows and trigger reporting automations.
GET /surveys/submissions
submission_id, survey_id, respondent, submitted_at
Trigger: Schedule a periodic sync.
Actions: Map survey metadata between Humi and Workflows and update dashboards.
GET /surveys/ (and related endpoints)
survey_id, status, last_updated
Automate data transfers without writing code, reducing manual work.
Get real-time data to power dashboards and reporting.
Accelerate onboarding and scale integrations across teams.
Learn the essential terms used in this integration, including API endpoints, authentication, and data mapping.
A defined interface that lets different software talk to each other.
The process of proving identity to access an API, typically via API keys or OAuth tokens.
A specific URL that performs an action or returns data in an API.
Permissions granted to an app to access certain resources or operations.
Auto-create welcome surveys in Humi when a new user signs up in your GHL-driven workflow.
Stream submissions into a central analytics view in GHL from Humi.
Trigger campaigns in your marketing suite when surveys are completed in Humi.
Create a GHL API key with surveys.readonly and connect it to Humi.
Enable GET /surveys/ and GET /surveys/submissions in your connection and test the data flow.
Run tests and turn on automation rules that trigger actions in Humi.
The Workflows API, with scope surveys.readonly, can access survey data and submissions from Humi as permitted. It does not grant write access unless you upgrade scopes. Use secure storage for keys and limit access to authorized users.
Currently, the available endpoints included GET /surveys/ and GET /surveys/submissions. Other endpoints exist but may be behind broader scope or not required for this page. Refer to the official API docs for a full list.
No heavy coding is required. Use the GHL connection screen to configure API keys and map fields. For advanced automations, some basic data mapping helps.
Test by running a manual fetch from the Test Connection button, verify the data appears in GHL and Humi, and monitor logs. Iterate until data flows as expected.
The required scope is surveys.readonly for reading surveys and submissions. You can request additional scopes if needed, depending on your use case.
The integration uses API keys or OAuth tokens; use HTTPS, rotate credentials, and follow best practices for credential management and access control.
API documentation for endpoints is available in the GHL developer docs and the Humi API docs; this page summarizes the key endpoints and how to call them.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
