The connection between a business's accounts and its software
AppConnect links the third-party accounts a company already holds — its calendars, its messaging and social channels, its advertising accounts, the systems its records live in — to the software workspace its team works in, and keeps the two in step.
Infrastructure, not an application
Nobody buys AppConnect, opens it or signs in to it. It is the part that asks a provider for permission, holds that permission safely, and does only the work that permission was granted for.
When a business connects an account, AppConnect is the name on the consent screen.
What AppConnect connects
Four kinds of account, each for one bounded job.
Calendars
Appointments booked in the workspace are written to the connected calendar and removed when they are cancelled, and the times already taken on that calendar are read so the same slot is never offered twice.
Built for: Google Calendar, Microsoft Outlook.
Messaging and social channels
Posts and replies go out to the pages and accounts a business runs, and the messages people send to those accounts arrive in the workspace, so a conversation is answered in one place instead of four.
Built for: Facebook Pages, Instagram, WhatsApp Business, Discord.
Advertising accounts
Spend and performance figures are read from the advertising account so they sit beside the results they produced, and a campaign can be paused or resumed without leaving the workspace.
Built for: Meta Ads.
Business records
Contacts, companies, deals and the notes attached to them are read out of the system a business is moving away from, so its history arrives with it. This direction is read-only: nothing is ever written back.
Built for: HubSpot, Salesforce, Zoho CRM, GoHighLevel.
Naming a provider above says what AppConnect is built to connect. It does not say the connection can be made today. Availability is listed below, provider by provider.
How a connection is made
Three things are true of every connection, on every provider.
The account holder authorises it
Permission is granted on the provider's own screen, by the person who holds the account. AppConnect never asks for, receives or stores the password of a connected account.
Only the agreed permissions apply
Each permission is requested for one stated job. AppConnect cannot widen what it may do afterwards without sending the account holder back to the provider to agree again.
It can be withdrawn at any time
A connection can be removed in the workspace, or revoked in the provider's own account settings, without notice and without asking us. The stored authorisation is deleted.
Signing in to a workspace
AppConnect also carries the consent screen when somebody chooses to sign in to a workspace with an account they already have, rather than creating another password. That is an identity check, not a connection.
It reads the name and email address on the account so the workspace knows who has arrived, and nothing else. Signing in this way grants no access to a calendar, a page, an advertising account, a message or a record.
Which permissions are requested, and what is kept, are set out in the Privacy Policy.
What is available today
Naming a provider on this page says what AppConnect is built to connect. It does not say the connection can be made today.
The availability page lists every provider and its current state, one by one — what can be connected now, and what is still in development and why.
It is deliberately the only page that states this. A status repeated in two places is a status that will eventually disagree with itself.
Google Calendar data AppConnect uses
For the calendar connection, AppConnect requests two Google OAuth scopes. Each one is requested for the single purpose described beside it, and for nothing else.
-
https://www.googleapis.com/auth/calendar.events
Why it is needed: to create, update and remove calendar events that correspond to appointments booked in the user's workspace. Without it, a booking made in the workspace could not appear on the user's calendar, and a cancellation could not remove it.
-
https://www.googleapis.com/auth/calendar.readonly
Why it is needed: to list the calendars on the account so the user can choose which one to connect, and to read busy and free periods on that calendar so the product does not offer a time the user is already booked for.
AppConnect does not request access to Gmail, Google Drive, Google Contacts, or any Google data outside the two calendar scopes above. Where a Google account is used to sign in rather than to connect a calendar, the only permissions requested are openid, profile and email, and those give no access to a calendar.
What AppConnect does with that access, how long it is kept, and how it is deleted are described in the Privacy Policy.
AppConnect's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Disconnecting
Any connection can be removed at any time, from either side.
In the workspace
Disconnect the account where it was connected. The stored authorisation is deleted, along with the data AppConnect had imported from that account for that connection, so it stops reading and writing immediately.
At the provider
Remove AppConnect's access in the provider's own account settings — for a Google account, at myaccount.google.com/permissions — which withdraws the authorisation from the provider's side.
What stays behind
Disconnecting does not undo what a connection already did. An event placed on a calendar, a post that was published, a message that was sent and a record that was imported all belong to where they now are, and stay there unless they are removed in that place.
Who operates AppConnect, and how to reach us
AppConnect is operated by Velocity Automation Corp. It is the integration service used by the business software platforms that Velocity Automation Corp operates, and by the customer workspaces running on them. It is not sold separately and cannot be used on its own.
For anything about the service or a connection, write to support@getappconnect.com. For anything about your data — including a request to delete it — write to privacy@getappconnect.com, which reaches the same people and keeps data requests in one place.
Those are the only channels we operate, and we never ask for account credentials by email. Nobody from AppConnect will ever ask you for a password, a one-time code or an API key.
Every permission, written down before it is asked for
What each connection requests, what it does with it, how long it is kept and how to have it deleted — all of it in plain sentences, provider by provider.
Read the Privacy Policy