Connecting an app
On this page
Connecting takes about two minutes per app. This page covers what you are actually agreeing to, where to find the values you will be asked for, and how to undo it.
Everything happens at Integrations. Click an app to open its panel — the panel lists exactly what the connection will be able to read and write before you start.
Two ways to connect
| Type | What happens | Which apps |
|---|---|---|
| Sign in | You are sent to the provider, log in as normal, and approve the access. No keys to copy. | Salesforce, HubSpot, Zoho, Dynamics 365, Google Calendar, Google Sheets, Gmail, Outlook, Slack, Meta |
| Keys and URLs | You paste values from your own system into a short form. | WooCommerce, n8n, Business Central |
Sign-in connections
Open the app and click Connect
You are redirected to the provider’s own login page — Google, HubSpot, Microsoft. You are typing your password into their site, not into Vociply.
Log in as the right person
This matters more than people expect. The connection acts as whoever authorises it. Sign in as an account that has access to the data the agent will need — and, ideally, one that will still exist when that person leaves.
Approve the access
The provider lists what Vociply is asking for. It matches the read and write list shown on the integration panel. If something looks broader than you expected, stop and ask — do not approve and hope.
You land back in Vociply, connected
The card now shows as connected. Some apps need one more step before they can do anything — see below.
Connecting as you@company.com works until you go on leave or change roles. Connecting as operations@company.com keeps working. For anything that will run in production, prefer the shared account.
Key and URL connections
Three apps need values you fetch from your own system. Each field in the form tells you where to find it.
WooCommerce
| Field | Where to get it |
|---|---|
| Store URL | Your shop’s address. Only the scheme and host are kept. |
| Consumer key | WooCommerce → Settings → Advanced → REST API → Add key. |
| Consumer secret | Shown once when you create the key. Copy it then. |
Give the key Read/Write if the agent should place or update orders, Read if it only answers “where is my order?”. Grant the smaller one if you are unsure — you can always widen it.
n8n
| Field | Where to get it |
|---|---|
| Webhook URL | From the Webhook node in the n8n workflow you want to trigger. |
| Header name / value | Optional. A shared secret so only Vociply can trigger it. |
n8n has no single host — everyone runs their own, self-hosted or on n8n.cloud — which is why it is a URL rather than a sign-in. The n8n playbook walks the whole thing.
Business Central
| Field | Where to get it |
|---|---|
| OData base URL | Your BC service tier’s OData endpoint. |
| SOAP base URL | The SOAP endpoint, for the calls OData cannot serve. |
| Company | The company code, e.g. NDU-K. |
| Username | A Business Central user with access to the pages you need. |
| Web service access key | Generated on that user’s BC user card. |
This one usually needs your IT person for ten minutes. See the Business Central playbook.
The extra setup step
Two integrations need one value that signing in cannot supply, and they will tell you so on the card until you provide it.
- Google Sheets — authorising Google grants access to the Sheets API, not to any particular spreadsheet. Paste the link to the sheet you want. Vociply opens it to check the connection really can, then saves it.
- Meta Lead Ads — signing in with Facebook authorises your account, not a Page. Choose the Page your lead forms belong to. Saving it also switches on lead notifications for that Page — a step that is invisible in Facebook’s own interface and the usual reason a setup that looks correct never receives anything.
The warning on the card is not cosmetic. Google Sheets with no spreadsheet chosen, or Meta with no Page, is connected but inert. Finish the step.
Access, storage and revoking
What Vociply can do with the connection
Only what the integration lists. The read and write capabilities shown on each panel are the complete set of actions the platform can perform — an agent cannot ask for something outside them, and there are no delete actions anywhere in the catalogue.
How credentials are stored
Keys and tokens are encrypted at rest, scoped to your account, and never shown back to you in full after saving. Where a provider issues refresh tokens, Vociply renews access in the background so connections do not silently expire.
Disconnecting
Disconnect from the integration’s panel. The connection and its stored credentials are removed, and any agent that was using it loses that ability immediately — so check which agents depend on it first.
You can also revoke from the provider’s side — Google’s connected apps, HubSpot’s installed apps, Facebook’s business integrations. Doing it there stops access even if you no longer have a Vociply login.
If an agent tries to use an integration that has just been removed, the lookup fails and the agent has to improvise. Change these outside business hours, or point the agent at a fallback instruction first.
Connection questions
Do I need to be an admin of the app I am connecting?
Not always, but you need an account with permission to see and change the data the agent will use. In Salesforce and Dynamics that often does mean an administrator; in Google Calendar it just means access to the calendar.
Can I connect two accounts of the same app?
One connection per provider per Vociply account. If you genuinely need two — two Google Workspaces, say — route the second through n8n.
My connection stopped working.
Usually the authorising user’s password changed, their account was disabled, or an admin revoked the app. Reconnect — ideally as a shared service account this time. For key-based connections, check whether the key was regenerated on your side.
Does connecting an app share my call recordings with it?
No. The flow is one-way: the agent asks the app for information, or writes a record to it. Recordings stay in Vociply unless you explicitly build something that sends them elsewhere.