01Who this is for
- Marketing agencies, automate AI qualification calls right after a lead form is submitted.
- Real estate firms, send AI driven appointment reminders to cut no show rates.
- Healthcare providers, deliver onboarding information through AI chat after patient intake.
02VAPI actions and triggers, explained
The VAPI integration adds two new directions to HighLevel workflows. As a trigger, VAPI can start a workflow when it creates a new assistant, call, or knowledge file. As an action, the workflow can command VAPI to place AI calls, start chats, upload files, or manage existing VAPI records.
All VAPI steps appear inside the workflow builder once a VAPI account is connected. Triggers poll every five minutes, and actions execute in real time when the workflow reaches them. The integration lives under Automation > Workflows and also under Settings > Integrations for account linking.
03How businesses use VAPI actions and triggers
- Digital marketing agency. The agency adds a VAPI Create a Call action after a lead form submission, maps the contact's phone number with {{contact.phone}}, and lets the AI qualify the lead without manual outreach.
- Dental practice. When a patient books an appointment, the practice adds a VAPI Create Chat action, uses merge fields like {{contact.first_name}} to send pre visit instructions via an AI chat session.
- Insurance broker. After a policy is sold, the broker adds an Upload File action, selects the policy PDF, and uploads it so the AI assistant can reference the document during future calls.
04The numbers and rules that matter
- Every VAPI account includes 10 concurrent call slots by default.
- Only one file can be uploaded per Upload File action step.
- Supported file formats:.md,.PDF,.txt,.log,.CSV,.tsv,.HTML,.CSS,.js,.ts,.xml,.json,.yaml,.yml,.doc,.docx.
- Triggers poll every 5 minutes.
05Before you start
- Access to Automation > Workflows
- A connected and active VAPI account
- Premium Workflow features enabled
06How to set up and use VAPI actions and triggers in HighLevel
Connect VAPI from Workflow Builder
- Navigate to Automation > Workflows.
- Add any VAPI trigger or action to the workflow canvas.
- Click the Connect Now button that appears.
- Authorize the VAPI account when prompted.
Connect VAPI from Integrations page
- Open Settings > Integrations.
- Select the VAPI option from the list.
- Click the Connect button.
- Complete the authentication flow to link the account.
Set up VAPI in a workflow
- Go to Automation > Workflows.
- Create a new workflow or open an existing one.
- Choose a trigger such as Form Submitted, Appointment Created, or Pipeline Stage Changed.
- Add a VAPI action, for example Create a Call.
- Map dynamic fields using merge values like {{contact.first_name}}, {{contact.phone}}, {{opportunity.name}}, or {{custom_values}}.
- Add conditions or Wait steps if needed.
- Test the workflow in draft mode.
- Publish the workflow to make it active.
07Settings that matter
- Default Concurrency. Sets the number of VAPI calls that can run at the same time; the default is ten concurrent slots.
- Increasing Concurrency. Allows you to raise the concurrent call limit via the Reserved Concurrency option in the VAPI dashboard billing settings.
- API Rate Limits. Limits the number of API requests based on your VAPI subscription tier and can affect how many actions run in a short period.
- Supported Phone Numbers. Restricts call initiation to phone numbers purchased directly inside VAPI; other numbers are not accepted.
- Upload File, Supported File Types. Limits each Upload File action step to a single file; multiple files require separate steps.
- Supported File Formats. Defines which document types can be uploaded as knowledge files, such as Markdown, PDF, TXT, LOG, CSV, TSV, HTML, CSS, JS, TS, XML, JSON, YAML, YML, DOC, and DOCX.
08Things to know before you rely on it
- Only ten calls can run concurrently by default; extra calls are queued.
- Each Upload File step accepts only one file; add more steps for additional files.
- Only VAPI purchased phone numbers can be used for calls; Twilio, HighLevel, or imported numbers are not supported.
- Triggers poll every five minutes, so real time reaction is limited to that interval.
- VAPI actions and triggers are billed as Premium Workflow steps.
09If something goes wrong
- Concurrency limit reached. Increase concurrency through Reserved Concurrency in VAPI billing settings.
- API rate limit exceeded. Add Wait steps and stagger call automation to stay within rate limits.
- Unsupported phone number used. Use a phone number purchased directly inside VAPI for call actions.
10How it connects to the rest of HighLevel
- Learn the basics of HighLevel workflow automation and how to set up triggers and actions. Workflow basics
- Enable premium workflow features required for VAPI actions and triggers. Enable premium features
- Step by step guide to creating workflows with triggers, filters, and actions. Workflow creation guide
Michael's take

The concurrency limit of ten calls means extra calls are automatically queued and retried as slots become available.
I test a single call in draft mode to confirm the merge fields and phone number format before publishing the workflow.