Integrations FAQ
This page covers common issues with CRM integrations (GoHighLevel and HubSpot), calendar connections, webhooks, and other third-party integrations.
GoHighLevel (GHL)
GHL connection keeps disconnecting
GHL OAuth tokens expire periodically. When this happens:
- Navigate to Integrations → GoHighLevel
- Click Disconnect
- Click Connect to re-authenticate
- Authorize the connection in the GHL popup
GHL token expiry is a known behavior of the platform. If you experience frequent disconnections, check that your GHL account has an active subscription and that BuildVoiceAI is listed as an authorized app.
Contacts not syncing from GHL
- Check the connection status — Ensure GHL shows as “Connected” on the integrations page.
- Verify scopes — The GHL integration requires contact read/write permissions. Disconnect and reconnect if scopes were changed.
- Check the sync log — View recent sync activity in the integration detail page for errors.
- Manual sync — Click the Sync Now button to force a sync.
GHL workflows not triggering calls
- Check workflow status — Ensure the workflow is enabled in the BuildVoiceAI workflow editor.
- Verify the trigger — Confirm the GHL webhook trigger is correctly configured.
- Check the agent — The workflow must reference an active agent with a phone number.
- Review execution log — Check Workflows → Execution Log for error details.
HubSpot
HubSpot sync failures
- Re-authorize the connection — HubSpot tokens can expire. Go to Integrations → HubSpot and click Reconnect.
- Check required scopes — Disconnect and reconnect to ensure all necessary scopes are granted. Required scopes include contacts, deals, and timeline events.
- Check HubSpot subscription — Some API features require a HubSpot Professional or Enterprise plan.
HubSpot refresh tokens are single-use. If a token refresh fails (e.g., due to a network issue), you must re-authorize the connection manually.
Contact properties not updating in HubSpot
- Check property mapping — Verify that BuildVoiceAI fields are mapped to the correct HubSpot properties.
- Check custom properties — If you are using custom HubSpot properties (like
ai_call_tags), ensure they exist in your HubSpot account. - Check API limits — HubSpot has API rate limits. High-volume operations may be throttled.
HubSpot tags not appearing
BuildVoiceAI uses a custom property called ai_call_tags in HubSpot. To ensure it works:
- Verify the
ai_call_tagsproperty exists in your HubSpot contact properties - Check that the property type is set to “single-line text”
- Tags are stored as semicolon-separated values (e.g.,
qualified;interested;follow-up)
Calendar Integrations
Google Calendar booking fails
- Check calendar connection — Verify Google Calendar is connected in Integrations.
- Check availability — Ensure the calendar has available time slots. The agent cannot book if the calendar is fully blocked.
- Timezone mismatch — Confirm the agent’s timezone matches the calendar timezone. Mismatches can cause bookings at unexpected times.
- Re-authorize — Google OAuth tokens can expire. Disconnect and reconnect the calendar.
Calendly links not working
- Verify the Calendly link — Ensure the link is valid and public.
- Check event type — The Calendly event type must have available times.
- Connection status — Verify Calendly is connected in Integrations.
Test calendar bookings manually before deploying to live calls. Create a test call and attempt a booking to verify the integration works end-to-end.
Webhooks
Webhook not firing
- Check the webhook URL — Ensure the URL is correct and publicly accessible.
- Check the workflow — The workflow containing the webhook action must be enabled.
- Check conditions — Verify the workflow conditions are met. For example, if the webhook only fires on completed calls, failed calls will not trigger it.
- Check the execution log — Go to Workflows → Execution Log to see if the workflow ran and what happened.
Webhook receiving errors
- Check your endpoint — Ensure your server returns a
200status code within 10 seconds. - Check HTTPS — Webhook URLs must use HTTPS.
- Check firewall — Your server must be accessible from the public internet.
- Check payload handling — Ensure your server correctly parses the JSON body.
Webhook signature verification failing
- Use the raw body — Compute the HMAC on the raw request body, not the parsed JSON.
- Use the correct secret — The secret for verification is your API key.
- Use timing-safe comparison — Standard string comparison can fail due to timing differences.
Slack
Slack notifications not appearing
- Check connection — Verify Slack is connected in Integrations.
- Check channel — Ensure the selected channel still exists and the BuildVoiceAI bot is a member.
- Re-authorize — Disconnect and reconnect the Slack integration.
General Integration Tips
- Always disconnect before reconnecting — This ensures a clean OAuth flow.
- Check the integration detail page — Most integrations show a sync log with recent activity and errors.
- Keep API keys current — If you rotate keys on the provider side, update them in BuildVoiceAI immediately.
Integration availability depends on your BuildVoiceAI plan. Some integrations require the Growth or Agency tier.