Skip to main content
Integrations

GoHighLevel Workflow Actions and Triggers

Every VoiceAIWrapper step in GoHighLevel workflows: add, update and remove leads, bulk lists, campaign status, client details, resources and the Form Submitted trigger.

Written By voiceaiwrapper

Last updated 26 days ago

Once a GoHighLevel sub-account is mapped to a client, its workflows can use VoiceAIWrapper steps. A workflow can drop a contact into a calling campaign, change or remove the lead later, pause a campaign, or read a client's account details to decide what happens next. A trigger can also start a workflow when a client submits a form in their client portal.

This article lists every step, what it needs and what it gives back.

Before you start

Leads added from GoHighLevel are called like any other lead, so they use AI credits or your provider account's minutes when the campaign dials them.

How the steps work

  • They act on the contact going through the workflow. You don't pick the lead from a list. VoiceAIWrapper finds the lead from the contact, within the campaign you choose on the step.
  • Every step is scoped to the mapped client. A sub-account can only touch its own client's campaigns, leads, forms and resources.
  • Running a step twice is safe. Adding a contact who is already in the campaign, or removing one who is already gone, counts as success.
  • Find the steps by app name. In the workflow builder, add an action and search for the app's name, not the step's name. The steps are listed under the app.
  • When a step is refused, the reason is in GoHighLevel. Open the workflow's execution log and the step's event details. A step refused by VoiceAIWrapper shows as failed, with a message that explains why. A step marked Skipped with no reason usually had a required field left empty, so GoHighLevel didn't run it.

Lead actions

These change one lead: the contact passing through the workflow.

Add Lead to Voice Campaign

Adds the contact to a campaign as a lead.

FieldWhat to put in it
CampaignPick from the dropdown. It lists the campaigns assigned to this client's workspace.
Phone, first name, last name, emailMap them from the contact. If the phone comes through empty, VoiceAIWrapper reads the phone, name and email from the contact instead.
Merge variablesOptional. One key=value per line. Each becomes a variable your agent can use during the call.
Update the contact after the callLeave it on, or untouched, to write notes, tags and fields back to the contact after each call. Turn it off for campaigns that shouldn't.

Merge variables can use GoHighLevel merge tags:

appointment_type=consultation
preferred_time={{contact.preferred_time}}

Write name=value. If a line has no =, a colon works too (name: value). Blank lines, lines starting with #, lines with no separator and empty values are skipped. To use these values in your agent's prompt, see Use Call Data and Variables in Your Prompt.

Before adding the lead, VoiceAIWrapper:

  • Checks do-not-disturb. A contact marked do-not-disturb for calls in GoHighLevel isn't added. See GoHighLevel Do-Not-Disturb Sync.
  • Cleans up the phone number. Everything except digits and a leading + is removed, such as spaces, brackets and dashes. A leading + is kept but never added, so store numbers in international format, for example +15551234567.

Update Lead in Voice Campaign

Changes a lead that's already in the campaign. Every field is optional, and a blank field leaves that value unchanged.

  • Phone, names and email: fill in only what should change.
  • Merge variables: if you fill this in, it replaces all of the lead's existing merge variables, not just the ones you list.
  • Do Not Call: when on, the lead stops being called. When off, nothing changes. A workflow can't turn do-not-call off.
  • Call again: when on, a lead that was answered is marked unanswered so the campaign calls it again.

If the contact isn't a lead in that campaign, the step fails with "This contact is not a lead in that campaign, so there was nothing to update. Add them with the 'Add Lead to Voice Campaign' action first."

Remove Lead from Campaign

Deletes the lead from the campaign.

Removing a lead also deletes its call history: every transcript, summary and cost record for that lead's calls. This can't be undone. To stop calling someone and keep the record, use Update Lead in Voice Campaign with Do Not Call on instead.

Get Lead Status

Reads where the contact's calls have got to, without changing anything. Use it with an If/Else branch. The most useful outputs:

OutputWhat it tells you
foundWhether the contact is a lead in that campaign. A contact who isn't comes back as false, not as an error.
answered, answered_atWhether, and when, a call was answered.
attempts_made, attempts_remainingHow many calls were made and how many are left before the campaign gives up.
next_attempt_atWhen the next call is due.
do_not_call, do_not_call_reasonWhether calling is stopped, and why.
invalid, invalid_reasonWhether the number was rejected as unusable.

Empty values come back as blank text or 0, never null, so they're safe to use in an SMS or email.

Bulk lead actions

These act on a list you supply in the step, not on the contact passing through. If the workflow runs for many contacts, the same list is processed each time.

ActionUp toHow it runs
Bulk Add Leads1,000 leadsQueued. The step reports how many leads were accepted and skipped, not the final result.
Bulk Update Leads200 leadsApplied straight away, lead by lead. Leads not in the campaign are counted, not treated as errors.
Bulk Remove Leads200 leadsApplied straight away. Deletes each lead and its call history.

A longer list is refused, not cut short. Split it into smaller runs.

Paste the list as JSON, or map a variable from an earlier step:

[
  { "phone_number": "+15551234567", "first_name": "Ana", "contact_id": "abc123" },
  { "phone_number": "+15559876543", "custom_fields": { "appointment_type": "consultation" } }
]
  • Plain phone numbers work too. Instead of JSON, you can supply phone numbers separated by commas or new lines. This is most useful for Bulk Add Leads and Bulk Remove Leads.
  • Include contact_id (the GoHighLevel contact ID) when you want call results written back. Without it, the leads are called but nothing reaches the contact. See Call Results in GoHighLevel Contacts.
  • Bulk Update Leads reads its instructions per lead: add "do_not_call": true or "call_again": true to the lead's entry. Unlike the single Update Lead in Voice Campaign step, "do_not_call": false turns do-not-call off for that lead. A custom_fields entry replaces all of that lead's merge variables.
  • Bulk Add Leads doesn't check do-not-disturb on each contact. Use Add Lead to Voice Campaign when that matters.

Bulk Remove Leads deletes the leads and all of their call history in one step. It can't be undone. Use Bulk Update Leads with "do_not_call": true to stop calling a list and keep the records.

Campaign action: Update Campaign Status

Changes the status of the whole campaign, not just this contact's lead. Every lead in the campaign is affected.

Ask forWorks when the campaign isResult
PausedActive or EndedCalling stops until you resume.
ActivePausedCalling resumes.
ScheduledDraftThe campaign is scheduled. If its start time has already passed, it becomes Active instead.
DraftScheduledThe campaign goes back to Draft.
EndedAny statusThe campaign ends.

If the campaign is already in the status you ask for, the step succeeds without changing anything. That matters because the step runs once for every contact. Other moves are refused with a message naming the problem, for example "cannot move to ACTIVE from current status". See Campaign Statuses and the Campaign Switch.

Client actions

These don't need a contact or a campaign. The mapped sub-account already tells VoiceAIWrapper which client and workspace to use.

ActionWhat it does
Get Client DetailsReads the client's account. Choose a section or all of them: client (email, users), plan (the client's subscription from your client billing: plan name, price, trial status), usage (minutes used, limit and remaining), campaigns (count, active count, names, lead count) or forms (submission count, form titles, latest submission). Campaigns and forms cover the whole client, across all of its workspaces.
Get Assigned ResourcesCounts what's assigned to the workspace and lists the IDs: agents, phone numbers, phone number pools, campaigns, knowledge bases, tools and more. Pick a resource type to narrow it down.
Assign Resources to ClientSets what the workspace has access to. Each resource type has its own list. The items you choose in a list replace that type's current assignments. Types you leave empty are left alone.
Get Form SubmissionReads the client's latest submission of a form you pick, plus how many times they've submitted it. Test submissions are left out unless you include them.

Assign Resources to Client replaces assignments. If you pick three campaigns, those three become the workspace's campaigns and any others are unassigned. Unassigned campaigns also disappear from this sub-account's campaign dropdowns. See Create a Workspace and Assign Assets.

The lists only offer resources from the workspace's own Pod (an engine or provider connection). For a workspace on VAW Native, only campaigns and phone number pools are offered, so agents, phone numbers and knowledge bases can't be assigned from GoHighLevel.

Trigger: Form Submitted

Starts a GoHighLevel workflow when a client submits one of your forms in their client portal. Add it as the workflow's trigger and filter by form if you only care about one.

The trigger gives later steps:

  • The form's title and when it was submitted.
  • Whether this is the client's first submission or an update to an earlier one.
  • The client's name and email.
  • The answers, as one block of text.

Things to know:

  • It fires in every mapped sub-account of that client. A client with two workspaces mapped to two sub-accounts triggers both.
  • Test submissions never fire it.
  • No contact is attached. A client fills in the form, not a contact in the sub-account. Steps that need a contact have nothing to act on. Steps such as internal notifications, webhooks or Slack messages work normally.

See Build Client Forms.

Example: call every new web lead

  1. Trigger: any GoHighLevel trigger that fits, for example a contact tag such as call-me being added.
  2. Action: Add Lead to Voice Campaign. Pick the client's outbound campaign, map the contact's phone and name, and add source=web_form as a merge variable.
  3. Wait: one day.
  4. Action: Get Lead Status on the same campaign.
  5. If/Else: if answered is false and attempts_remaining is 0, send the contact a follow-up SMS.

After each call, the contact also gets a note, an outcome tag and updated AI Call fields. See Call Results in GoHighLevel Contacts.

Troubleshooting

The sub-account isn't mapped, the app was removed from it, the client is disabled, the connection needs reconnecting, or your plan no longer includes GoHighLevel integration. Check the sub-account's row in Settings β†’ Integrations β†’ Manage sub-accounts. See Connect GoHighLevel and Map Sub-Accounts.

No campaigns are assigned to the workspace this sub-account is mapped to, or the sub-account isn't mapped. Assign the campaign to the workspace, then reopen the step. See Assign a Campaign to a Client.

The campaign chosen on the step was unassigned from the workspace, or the sub-account was mapped to a different workspace. Assign it again, or pick another campaign on the step.

The number isn't in a format that can be dialled. Store phone numbers in GoHighLevel in international format, with + and the country code, for example +15551234567.

The phone field on the step was empty and the contact has no phone number in GoHighLevel. Add a number to the contact, or map the right field.

You're testing the step outside a real workflow run, so no contact is attached. Fill in the phone field to test it, or run the workflow on a real contact.

Split the list into smaller runs: up to 1,000 leads for Bulk Add Leads, or up to 200 for Bulk Update Leads and Bulk Remove Leads.