Connect an integration

Integration connections are workspace-scoped. Connect a provider once, then create reusable integration functions that expose selected actions to the appropriate agents.

Supported connections

Provider	Connection method	Setup
Google Calendar	OAuth	Complete Google consent in the provider window.
Outlook Calendar	OAuth	Complete Microsoft consent in the provider window.
Jobber	OAuth	Complete Jobber consent in the provider window.
Clio Manage	OAuth	Complete Clio consent in the provider window.
Clio Grow	OAuth	Complete Clio Grow consent in the provider window.
Filevine	Secure credentials	Personal access token, client ID, and client secret.
Open Dental	Secure credentials	Customer key.
Email	Secure setup	Destination email address.

OAuth connections open an external consent flow. Credential-based and Email connections open the secure Integrations setup panel.

warning

Never place passwords, OAuth tokens, API keys, client secrets, or customer keys in Vox chat, an agent prompt, variables, or function descriptions. Enter them only in the provider consent screen or Wirevox secure integration setup.

Connect a provider

1. Open workspace Integrations settings.
2. Select the provider.
3. Complete OAuth consent or the secure setup fields.
4. Return to Wirevox and confirm Connected.
5. Create one integration function for the workflow and select its required actions.
6. Attach it to the intended agent.
7. Add exact action markers and rules to the prompt.
8. Test with controlled external data before publishing.

Vox can guide the process and open the appropriate connection screen. It must not ask you to paste secrets into chat. Consent or protected setup still requires an authorized user.

Select actions by least privilege

Enable only the subset the agent needs. For example, an intake agent may need calendar availability and booking but not cancellation. A receptionist may need Jobber lookup and request creation but should create a lead only when no client exists.

One integration function can include several actions from the same provider. This is preferable to creating one function per action when the actions form one workflow. Each live action still has its own exact marker and rules.

Connection state and function state

State	Meaning
Provider connected	Wirevox has a valid workspace connection.
Integration function created	A reusable subset of provider actions exists.
Function attached	One agent draft can access those actions.
Prompt rules added	The agent has an explicit policy for using them.
Agent published	The tested draft is promoted to live use.

If a provider becomes disconnected, reconnect it, verify status, run a controlled test, and monitor the first live uses.

Provider naming

Do not instruct the agent to announce internal provider names unless that is part of the customer experience. It can say “I can create your service request” without naming the CRM behind the action.

Next step

Continue with Write function rules in the system prompt.