Setting Up Outbound AI Voice Calls Using a Webhook (No Premium Action Required)

Outbound AI voice calls are a powerful tool for automating client outreach. The recommended method has shifted from using the "Make AI Call" premium action to a more reliable and cost-effective approach: using a standard webhook. This offers greater control, fewer delays, and saves on premium workflow costs.

---

Why Use a Webhook Instead of "Make AI Call"?

• Reduced Delays: Webhooks process faster and are easier to troubleshoot.
  
  

• No Premium Fees: Standard webhooks don't count as premium actions in your workflow system.
  
  

• More Transparent: You have full control over what data is sent, and can quickly see what's working.
  
  

---

Step-by-Step: Outbound Call via Webhook

1. Set Up the Webhook Action

• In your GoHighLevel workflow, add an action and select “webhook.”

2. Gather Required Data

Example: 

POST https://api.assistable.ai/v2/ghl/make-call

 

  "assistant_id": "173...00",

  "contact_id": "W15T...q1c",

  "location_id": "8X...n3",

  "number_pool_id": "hJb...pfT" // this one is optional

Authorization: Bearer asst_6...aeb92

 

You’ll need to send the following with your webhook:

• Assistant ID:
  

  • Find this in your AI assistant editor (click the ellipsis and copy the bot/assistant ID).

• Contact ID:
  

  • Use the variable picker in your workflow to select the contact’s ID.

• Location ID:
  

  • Go to Settings > Business Profile in your CRM to find the location/account ID.

• Authorization Key:
  

  • In your agency workspace, navigate to Integrations > API Keys.
    
    

  • Generate a Version 2 key (enter your password if prompted).
    
    

  • Format your header as Authorization: Bearer [API_KEY] (make sure there is one space after "Bearer" and no extra spaces).

If using number pools for high-volume outbound calls, include the pool ID as an additional body field.

3. Fill in the Webhook Details

• Body: Add Assistant ID, Contact ID, Location ID (and Pool ID if needed).
  
  

• Header:
  

  • Authorization: Bearer [YOUR_API_KEY]
    
    

  • Accuracy matters—incorrect formatting can break the workflow.

4. Save and Test the Workflow

• Save your changes.
  
  

• Run a test with a sample contact.
  
  

• If the call doesn’t come through, check the following:

  • The workflow is turned on.
    
    

  • All IDs and tokens are correct.
    
    

  • The header formatting is exact (no extra spaces or typos).
    
    

🛠️ Tip: If calls are slightly delayed, it’s normal during high volume. Double-check your workflow status and all variables if you experience issues.

---

Troubleshooting

• If the call doesn’t go through, ensure:

  • The workflow is enabled.
    
    

  • All required variables are present and accurate.
    
    

  • The authorization header is formatted correctly (Bearer [API_KEY]).
    
    

  • You are using a Version 2 API key for this integration.
    
    

• For number pools, ensure the correct pool ID is sent in the webhook body.