Start by creating an API key in your GHL account and grant DropFunnels the required scope surveys.readonly to read surveys and submissions.
In the GHL apps area, authorize the DropFunnels integration so it can access surveys and submissions. When prompted, grant the necessary permissions.
Endpoint 1: GET /surveys/ — fetches the list of surveys in your GHL account. Endpoint 2: GET /surveys/submissions — retrieves responses for the surveys. Additional endpoints may be available for extended functionality; only the relevant endpoints are shown here for the DropFunnels connection.
When a new survey submission is received, trigger a DropFunnels workflow to qualify the lead.
Update contact fields, enroll in nurture, and send a follow up email based on submission data.
GET /surveys/submissions
survey_id, submission_id, respondent_email
Periodic fetch of surveys to segment contacts based on responses.
Update lists, trigger scoring, or tag segments in DropFunnels.
GET /surveys/
survey_id, title, date_created
On submission completion, trigger a confirmation sequence in DropFunnels.
Notify team, trigger task creation, and log the outcome.
GET /surveys/submissions
submission_id, status, respondent_email
Build powerful automations without writing code. Use triggers and actions to move data between surveys and campaigns.
Quickly connect survey insights to customer journeys and personalize every message.
Centralize data flow in a single no code workflow for scalable campaigns.
This glossary explains endpoints, triggers, actions, and fields used in the DropFunnels and GHL integration.
A URL path that your app uses to access data from GHL through the Workflows API.
A completed response from a survey captured by GHL.
A set of questions and responses collected from a contact.
An event in a workflow that starts a sequence of actions.
Capture new respondent data and feed it into drip campaigns in DropFunnels.
Use survey responses to assign scores and route contacts to the right sequences.
Mark contacts as completed and trigger follow ups based on survey outcomes.
In GHL, create an API key with surveys.readonly scope and authorize the DropFunnels integration.
Add the endpoint URLs for GET /surveys and GET /surveys/submissions to your workflow triggers.
Create a test workflow, run a sample survey submission, and verify data in DropFunnels.
No code is required. The Workflows API lets you pull data into DropFunnels using triggers and actions, so you can automate without writing code. If you need more complex logic, you can combine multiple steps in a single workflow and test with a sample submission.
You primarily use GET /surveys/ and GET /surveys/submissions. These endpoints fetch survey definitions and responses. New data can be used to segment, tag, and trigger flows in DropFunnels.
surveys.readonly scope permits read access to surveys and submissions. It does not allow edits. Ensure the scope is granted to the app connection.
Authentication is via an API key generated in GHL and attached to the DropFunnels app. Copy the key and paste into the DropFunnels connection settings. Keep the key secret and rotate if needed.
Yes. You can test using sandbox or a test submission. Use a test survey submission and verify in the DropFunnels activity log or in the GHL test results.
View automation results in DropFunnels analytics and the GHL activity log. You can also inspect API call history in your GHL account.
If a survey is updated, your workflow can be configured to fetch the latest data on a schedule. If a survey is deleted, ensure your workflow handles missing data gracefully and uses fallbacks.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
