Documentation Index
Fetch the complete documentation index at: https://docs.vh3.ai/llms.txt
Use this file to discover all available pages before exploring further.
Native Integrations
VH3 AI connects to the tools your business already runs on. Not through middleware, not through point-to-point custom code, and not through a workflow builder. Native integrations are activated directly inside the platform — each user connects their own accounts, or an admin connects shared accounts at the organisation level, and the intelligence layer immediately starts drawing from those sources.
Every new connection makes the intelligence richer. The platform does not treat integrations as data pipes. It treats them as additional context that deepens the operational picture.
How connections work
Integrations in VH3 AI operate at two levels:
Per-user connections. Each team member can authenticate their own accounts — personal Gmail, Google Drive, Outlook, calendar — so their individual context flows into the intelligence layer. Pre-visit briefings can pull from the email thread between that engineer and the client. Reports can reference documents in a personal Drive folder. The intelligence is scoped to what that user has connected, not a shared service account.
Organisation-level connections. Shared tools — accounting platforms, CRM, project management, communication channels — are connected once by an admin and made available across the organisation. Xero connects once and real invoice and payment data starts flowing into financial reporting. Slack connects once and sentinel alerts start routing to the right channels automatically.
Connections are activated with a single authentication step inside the platform. No API keys to manage. No developer involvement. No waiting on a roadmap.
Available integrations
Accounting and finance
| Integration | What it enables |
|---|
| Xero | Real invoice and payment data into operational reporting. Stop inferring payment status from job records alone. |
| QuickBooks | Same financial intelligence for QuickBooks-based operations. |
| Stripe | Payment and customer data connected to the operational picture. |
CRM and sales
| Integration | What it enables |
|---|
| Salesforce | Account history, pipeline, and contact context alongside operational data. |
| HubSpot | CRM activity and deal context connected to job and site intelligence. |
| Pipedrive | Pipeline sync so account managers see operational and commercial context in one place. |
| Zoho CRM | Contact and account sync into the intelligence layer. |
Communication and email
| Integration | What it enables |
|---|
| Gmail | Per-user authentication. Email threads linked to jobs, sites, and customers. Inbound mail parsed and matched against the knowledge graph. |
| Outlook | Same for Microsoft-based operations. |
| Microsoft Teams | Sentinel alerts, briefings, and reports delivered to channels. |
| Slack | Operational intelligence routed to the right channels and people automatically. |
| WhatsApp | Alerts and notifications to field managers and account teams. |
Cloud storage and documents
| Integration | What it enables |
|---|
| Google Drive | Per-user and shared drive sync. Documents, reports, and compliance files linked to sites, engineers, and jobs. |
| OneDrive / SharePoint | Same for Microsoft-hosted document libraries. |
| Dropbox | Document sync for Dropbox-based operations. |
| Google Docs | Document content searchable alongside job and site history. |
| PandaDoc | Agreements and signatures linked to accounts and cases. |
Productivity and project management
| Integration | What it enables |
|---|
| Google Calendar | Per-user calendar sync. Scheduling context connected to job planning. |
| Google Sheets | Data sync for teams that use Sheets as a reporting surface. |
| Asana | Sentinel findings and operational actions pushed to tracked tasks. |
| Trello | Board and card sync for teams using Trello for follow-up tracking. |
| Jira | Issue creation and tracking linked to operational cases. |
| Monday.com | Work items connected to intelligence layer outputs. |
What each connection adds
The integrations above are foundations, not endpoints. What they provide today is connectivity — data flowing in, messages flowing out. What they grow into is intelligence.
A Xero connection today syncs invoice records. As the intelligence layer builds context, it connects payment patterns to specific customers, engineers, and job types — so commercial performance and operational performance are read from the same picture.
A Gmail connection today links email threads to jobs. Over time, it becomes part of the pre-visit briefing — “here is what was said in the last three emails with this facilities manager before the last visit.”
A Google Drive connection today makes documents searchable. It becomes the compliance layer — certificates, RAMS, site access instructions, and service reports linked to the right site and surfaced automatically when they are relevant.
Every tool you connect makes the intelligence richer. Not another silo. The same operational brain, with wider reach.
Adding integrations to your account
Integrations are managed from the Connections section of your VH3 AI account. Admins can connect organisation-level tools and manage which integrations are available to the team. Individual users connect their own accounts from their profile settings.
If you need an integration that is not currently listed, contact support. The connector library is expanded regularly.
