Connect your business systems

Verbatik connections belong to the selected workspace. Use an account your business owns or is authorized to manage. Your vendor subscription, API access and administrator permissions remain separate from Verbatik voice usage.

Connect an account

1. Open Integrations in your workspace and choose the service.
2. Use Connect for an available OAuth provider. Sign in to the business account and approve the requested resources. Google or Microsoft sign-in to Verbatik does not connect your calendar or files automatically.
3. For a token-based provider, obtain its API credentials from your own vendor account. Enter them in the connection's credential fields. Keep credentials out of prompts, knowledge files, URLs and support messages.
4. Enable writes only for the actions you intend to use. A read-only account cannot book an appointment or update a CRM record.
5. Run Test connection. Most tests read account metadata; they do not prove a booking, message or CRM update has succeeded.
6. Add the intended actions to the agent, save the draft and publish the version you will use for calls.
7. Test a read, then an explicitly authorized write in your own sandbox. Confirm the provider record and the action receipt in Verbatik.

Three connection types

• Workspace OAuth connectors: HubSpot, Salesforce, Google Calendar, Google Drive, OneDrive and Notion. Verbatik operates the application registration; you authorize your account. An organization administrator may need to approve the app.
• Native API apps: named actions and provider-specific settings for CRM, scheduling, support, industry and automation services. Some support renewing your supplied OAuth credentials; others require reconnecting when their token expires.
• Custom tools: an HTTP API or MCP server operated by you or an approved vendor.

Availability and validation

A catalog entry is not a promise that your subscription includes API access. Booksy, Denticon, Medatixx and Doctoranytime require vendor-approved contracts and sandbox access before callable operations can be enabled. Other API adapters have contract and safety tests; your account still needs a live validation pass.

For a veterinary practice-management system without a supported API connection, use an appointment-request workflow with staff confirmation. A Google Calendar event is not automatically a booking in ezyVet, Vetspire, Cornerstone, AVImark, Animana or Provet.

Troubleshooting

• 401: reconnect or renew the account token. Check that its tenant, region and environment match the saved connection.
• 403: ask the vendor administrator to check scopes, user roles, object permissions and API plan access.
• Missing records: check selected resources, location/calendar IDs, account region and filters.
• Write rejected: inspect required fields, picklists, availability, permissions and provider validation rules.
• Unknown outcome: verify the vendor record before retrying. A timeout after a write does not prove nothing happened.

For support, provide the provider name, failed action, timestamp and sanitized error. Never share passwords, tokens, secret webhook URLs or patient records.