Before you connect
- A Burki workspace administrator account and a saved assistant.
- Permission to install apps in the intended HubSpot account. Check the account shown on the authorization screen before granting access.
- The HubSpot connection must be configured on your Burki deployment. If setup is unavailable, contact Burki rather than adding credentials to an assistant prompt.
Review Burki usage pricing and your provider’s plan before a live test. Telephone calls, phone numbers and optional SMS can add charges; this guide does not promise a free provider plan.
Access and permissions
Burki requests contact read and contact write access, plus the standard OAuth authorization scope. The connection belongs to the workspace; selected assistant actions control how it is used.
Lookup uses an exact email address. The integration can create or update contact details and attach a short factual note to an existing contact.
This is on-demand CRM access, not continuous synchronization of the whole CRM. It does not upload call recordings or provide actions for deals, companies or tickets.
Connect and configure
Start from the right workspace
Open Integrations in Burki and select HubSpot. Choose Connect HubSpot. Sign in to HubSpot if requested.
Review the account and access
Select the intended HubSpot account, review the consent screen and authorize Burki only if you accept the requested access and any provider warnings.
Check the connection
On return to Burki, confirm the connected account and choose Test connection. This check reads from HubSpot; it does not change contacts.
Choose assistant permissions
In a saved assistant’s Actions tab, add HubSpot and choose lookup, contact saving and call-note actions separately. Require the caller’s confirmation before saving details or notes. Save and publish when ready for real calls.
Test the workflow
Browser practice simulates HubSpot actions. Use it to review what the assistant says and which actions it selects without changing your CRM.
A successful connection test confirms access, not a complete voice workflow. To verify real writes, use a separately authorized live call with a test contact, then inspect the contact and note in HubSpot. Do not use sensitive customer information for a demonstration.
Troubleshooting
- HubSpot says the account cannot install
- Check the installer’s HubSpot permissions and the app’s account eligibility or installation limit. Burki cannot bypass a provider restriction. Share the non-sensitive error with support.
- Reconnect required
- A workspace administrator should use Reconnect HubSpot and review the account and permissions again, then run Test connection. Check the assistant’s enabled actions before another live call.
- Contact not found
- Confirm the exact email address. Lookup does not search for a similar name or automatically create a contact. Enable contact saving separately if your workflow needs it.
- A save or note outcome is uncertain
- Inspect the relevant HubSpot contact and note before authorizing another write. A failed response does not prove nothing was saved.
Disconnect safely
- Remove the HubSpot actions from an assistant to stop that assistant using them.
- Choose Disconnect HubSpot in workspace Integrations to remove Burki’s stored connection and disable its local assignments.
- Uninstall Burki separately in HubSpot’s Connected Apps to remove the provider-side installation. Contacts and notes already saved in HubSpot remain there.
Data and support
Contact information flows between HubSpot and Burki for the enabled actions; confirmed notes flow to HubSpot. Disconnecting the connection does not delete CRM records, Burki call history or operation receipts. Manage provider records in HubSpot and use Burki’s privacy contact for data requests.
Burki’s privacy policy explains retention and data requests. Your workspace settings and applicable terms govern your account. Disconnecting an integration is separate from requesting deletion. See the terms of service for service conditions.
Need help with this connection?
Include the provider, workspace name, approximate time and a redacted error message. Never send API keys, authorization codes, payment links, card details or customer call content.
Contact Burki support