GoHighLevel Survey Submitted Trigger: Setup Guide (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 20 October 2026 · 9 min read
The GoHighLevel Survey Submitted trigger starts a workflow the moment a contact completes one of your surveys, which makes it the natural home for qualification, routing and intake logic. If your survey asks the right questions, the workflow can do the sorting your team currently does by hand.
This guide is part of our workflow-trigger series. I'll walk through how the HighLevel survey trigger works, which filters it offers, how to branch on answers with If/Else, and three real builds we use with clients: a trade quote qualifier, a clinic intake survey and an agency onboarding survey.
Quick Facts
| What fires it | A contact submitting a survey built in the HighLevel survey builder |
| Trigger filters | Which survey (one or several) and whether the submission was disqualified (true or false) |
| No survey selected | The trigger fires on any survey in the sub-account |
| Disqualification | Set inside the survey's conditional logic, then read by the trigger's Disqualified filter |
| Forms | Form submissions do not fire this trigger; they use the separate Form Submitted trigger |
| Official doc | HighLevel help centre article "Workflow Trigger - Survey Submitted" |
How the GoHighLevel Survey Submitted trigger actually works
A survey in HighLevel is a multi-step experience: questions sit on slides, and the respondent moves through them one screen at a time. When they reach the end and submit, the contact record is created or updated and the Survey Submitted trigger fires.
Every question you map to a standard or custom field writes its answer onto the contact. That is the important part, because your workflow branches on contact fields, not on the survey itself. If an answer isn't mapped to a field, your automation can't easily see it later.
Where to find it
Open Automation, create or edit a workflow, and add a new trigger. Survey Submitted sits with the other contact-based triggers in the trigger list. Give the trigger a clear name, such as "Survey: Quote Qualifier", so you can tell triggers apart when a workflow has several.
The two filters you get
Per HighLevel's Survey Submitted trigger documentation, the trigger offers two filters:
- Survey is — pick one or more surveys. Leave it empty and every survey in the sub-account will fire the workflow.
- Disqualified — true or false, based on whether the survey's own logic disqualified the respondent.
That's deliberately lean. Anything more specific, like "budget is above a threshold" or "service type is emergency", belongs in If/Else conditions after the trigger, which I cover below. If you want a refresher on how filters stack, our guide to the Form Submitted trigger setup walks through the same pattern on the forms side.
HighLevel survey trigger vs Form Submitted: which one fires?
This is the single biggest source of "my workflow didn't run" tickets we see. Forms and surveys look similar in the builder, but they are different assets with different triggers. A survey will never fire a Form Submitted workflow, and a form will never fire a Survey Submitted one.
| Aspect | Survey Submitted trigger | Form Submitted trigger |
|---|---|---|
| Asset type | Surveys (multi-slide, one step at a time) | Forms (single page of fields) |
| Built-in branching | Conditional logic can skip slides or disqualify | No slide logic; all fields on one page |
| Trigger filters | Which survey; disqualified true/false | Which form was submitted |
| Disqualification path | Native, via the Disqualified filter | Built manually with If/Else on field values |
| Best fit | Qualification, quizzes, intake, onboarding | Short opt-ins, contact and callback requests |
| Typical friction | Lower per screen, longer overall | Everything visible at once |
Choose the asset based on the conversation you want, not the trigger. We cover that decision in depth in our forms vs surveys comparison for lead capture.
Building disqualification paths with the survey trigger
Disqualification is what makes surveys more powerful than forms for qualification. Per HighLevel's conditional logic in surveys article, you add a rule in the survey's conditional logic panel, choose the disqualify action, and set the question, operator and value that should end the survey.
The same article notes that conditional logic is available on newer surveys, so if you're working on an old survey and can't find the option, clone it and rebuild the logic on the copy.
Two workflows, not one
My preferred setup is two separate workflows on the same survey:
- Qualified workflow — Survey is "Quote Qualifier", Disqualified is false. This one creates the opportunity, notifies the team and books follow-up.
- Disqualified workflow — Survey is "Quote Qualifier", Disqualified is true. This one tags the contact, sends a polite redirect or resource, and stops.
Splitting them keeps each workflow readable and stops a disqualified lead from slipping through a mis-set branch into your sales pipeline.
Test the disqualify behaviour yourself
There's a request on HighLevel's ideas board from users reporting that immediate disqualifications didn't always behave as they expected in workflows, and that partial submissions can still create contacts. I can't confirm the current status, so treat it as a reason to test with a real submission before going live rather than as a known bug.
Branching on survey answers with If/Else
Once the trigger fires, the answers live on the contact. Add an If/Else action straight after the trigger and build branches on the custom fields your survey populated.
Typical branch conditions look like this:
- Service type equals a particular option (for example, "Emergency repair" vs "New install").
- Budget range is one of your higher bands.
- Timeframe is "This week" or "This month".
- Location or postcode field contains a value inside your service area.
Keep one decision per If/Else where you can. Stacking five conditions into one branch makes it hard to see why a contact ended up where they did. Our walkthrough of If/Else branching logic in GoHighLevel workflows covers AND/OR grouping and the "None" branch in detail.
Tagging from answers
Tags are still the fastest way to make survey answers visible across smart lists, other workflows and reporting. In each branch, add a tag that describes the outcome, such as "survey-quote-emergency" or "survey-intake-new-patient". Use a consistent prefix so all survey-generated tags sort together.
Scoring from answers
If you run lead scoring, the survey is your richest input. In each branch, add or adjust points on a numeric custom field: more for urgent timeframes and higher budgets, fewer for "just researching". Then let a later step act on the total. Our guide to setting up lead scoring in workflows shows how to structure the score field so it doesn't double-count when someone resubmits.
Routing to pipelines and owners
The final job of most survey workflows is to put the lead in front of the right person. Use the Create/Update Opportunity action to drop qualified leads into the correct pipeline and stage, then assign an owner based on the branch. For round-robin or territory rules, see our Assign To User contact owner rules.
Real GoHighLevel survey trigger examples
Trade quote qualifier
A plumbing or electrical business asks job type, urgency, property type, suburb and rough budget across a handful of slides. Out-of-area suburbs trigger the survey's disqualify rule.
- Disqualified true: tag "out-of-area", send an SMS recommending they contact a local trade, end.
- Disqualified false, urgent: create opportunity in "Emergency Jobs", notify the on-call tech by SMS, assign owner.
- Disqualified false, standard: create opportunity in "Quotes", send a booking link for an on-site quote.
Clinic intake survey
An allied health clinic sends new patients an intake survey before their first appointment. Questions cover reason for visit, referral source and whether they have a referral letter.
- Branch on reason for visit to tag the right practitioner type and assign the contact owner.
- If a referral letter is required but marked "No", send a reminder task to reception.
- Write a note summarising key answers so the practitioner sees it in the contact record.
Keep anything clinically sensitive out of tags and SMS bodies. Store it in fields with appropriate access, and only send what's needed.
Agency onboarding survey
For agencies, a post-sale onboarding survey collects brand assets, logins needed, target audience and preferred launch date. The workflow tags the services purchased, moves the opportunity to an "Onboarding Received" stage, creates internal tasks for the account manager and sends the client a confirmation with next steps.
Testing your HighLevel survey trigger before launch
Never publish a survey workflow without pushing real submissions through it. My checklist:
- Save the workflow and switch it from Draft to Publish. A draft workflow won't enrol anyone.
- Submit the live survey with a test contact for every branch, including one that should be disqualified.
- Check the workflow's execution history to confirm which path each test took.
- Open the test contact and confirm fields, tags, owner and opportunity are all correct.
- Check the workflow's re-entry setting matches how you want resubmissions handled.
Use a fresh email address or phone number for each test run, or delete the test contact between runs. Otherwise duplicate rules can merge submissions and muddy your results.
Common mistakes to avoid
- Using Form Submitted for a survey. It will never fire. Surveys need the Survey Submitted trigger.
- Leaving "Survey is" empty. Every survey in the sub-account then enrols contacts, including old test surveys.
- Not mapping questions to custom fields. If the answer isn't stored on the contact, If/Else can't branch on it.
- Handling disqualified leads in the same workflow as qualified ones. Two workflows filtered on Disqualified true/false are cleaner and safer.
- Skipping live tests. Test every branch with a real submission, especially disqualification paths.
- Inconsistent tag names. Survey-generated tags without a shared prefix become impossible to report on within months.
If you want survey-driven qualification workflows built and tested in your sub-account, book a strategy call with the HL Growth Partner team.
Frequently asked questions
What does the GoHighLevel Survey Submitted trigger do?
It starts a workflow whenever a contact submits a survey built in HighLevel's survey builder. You can limit it to specific surveys and filter on whether the submission was disqualified. Everything after that, such as tagging, scoring and routing, is handled by the workflow actions you add.
Why isn't my survey firing my Form Submitted workflow?
Forms and surveys use different triggers in HighLevel. A survey submission only fires the Survey Submitted trigger. Add that trigger to your workflow, select the survey, and re-test with a live submission.
Can I filter the HighLevel survey trigger by a specific answer?
The trigger itself offers filters for which survey and whether the contact was disqualified. To act on a specific answer, map the question to a custom field and use an If/Else action after the trigger. That approach is also easier to read and maintain.
How do I disqualify someone in a GoHighLevel survey?
Open the survey's conditional logic settings, add a rule, and choose the disqualify action with the question, operator and value that should end the survey. In your workflow, use the Disqualified filter set to true to handle those contacts. If you can't see conditional logic on an older survey, clone it and rebuild the rules.
What happens if I leave the "Survey is" filter empty?
The workflow will fire for every survey in the sub-account. That includes old, test and duplicate surveys you may have forgotten about. Always select the specific survey or surveys the workflow is meant for.
Should I use a survey or a form for lead qualification?
Surveys suit qualification because they present one step at a time and support conditional logic, including disqualification. Forms suit short opt-ins where you only need a few details. Pick the asset that matches the conversation, then use the matching trigger.
How do I test a Survey Submitted workflow?
Publish the workflow, then submit the live survey with a test contact for each branch, including a disqualified path. Check the workflow's execution history and the contact record to confirm tags, fields, owner and opportunity. Use a fresh test contact for each run to avoid duplicate merging.
Related Articles on HL Growth Partner
More workflow triggers
- GoHighLevel Workflow Trigger Filters Explained (2026)
- GoHighLevel Contact Changed Trigger: Setup Guide (2026)
- GoHighLevel Pipeline Stage Changed Trigger (2026)
Workflow actions and data hygiene
- GoHighLevel Update Contact Field Action: Workflows (2026)
- GoHighLevel Tags Strategy: Naming, Structure and Hygiene (2026)
