Connect the tools you already run on
Sync your directory and devices from Microsoft, pull in your remote-access estate, automate the rest through Zapier — or build exactly what you need on a REST API that covers the whole product.
Get Started Free Read the API DocsMicrosoft Entra ID & Intune
The deepest integration in the product. Users and devices flow in automatically, carrying their live security posture — and you can act on them without opening another console.
- Sync users into clients and devices into assets
- Choose the cadence — manual, 3-hourly, daily, weekly or monthly
- Intune compliance state, BitLocker encryption and Defender health per device
- Force an Intune check-in or start a full Defender scan remotely
- Retrieve LAPS and BitLocker recovery keys — every access is logged
- Optionally disable records automatically when a device leaves your tenant
LogMeIn Central
Bring your LogMeIn estate in as assets, then start a remote control session straight from the device record.
- Import LogMeIn hosts as Vertask assets
- Manual or automatic sync every three hours
- Launch Remote Control from the asset without re-authenticating
- Credentials are exchanged server-side and never reach the browser
Zapier
Wire Vertask to thousands of other apps without writing anything. Useful when the system you need to connect has no direct integration.
- Create tickets, assets and clients from any Zapier trigger
- Pull assets and clients out to feed other tools
- Optionally auto-invite people to the client portal as they are created
- A rotatable connection token you control
Email to ticket
Point a mailbox at Vertask and messages become tracked tickets — with the quoting mess handled properly.
- Reply threading that survives Gmail, Outlook, Apple Mail and Yahoo quoting
- Quoted history stripped, so the ticket shows the actual new message
- Urgent-sounding subjects escalate priority automatically
- Unknown senders can become clients, subject to your rules
- Route different inbound addresses to different teams
REST API
Everything the interface does is available programmatically — over 200 endpoints spanning every part of the product.
- Tickets, assets, clients, contracts, projects, properties, KB and more
- Named API keys you can revoke individually, without breaking the others
- Every request logged with endpoint, status, duration and origin IP
- Full reference documentation with request and response examples
Twilio
Used specifically to deliver multi-factor authentication codes by text — not a general messaging channel.
- SMS delivery for multi-factor sign-in codes
- Falls back to email codes automatically if unavailable
The same surface powers the AI
Insight AI is built on the very same authenticated endpoints as the public API — which is why it can act across your whole workspace, and why it can never do anything your own permissions would not allow.
Meet Insight AIFrequently asked questions
Do you integrate with Google Workspace?
Not for automatic sync — directory and device syncing is Microsoft Entra ID and Intune only. Devices from any platform, including Chromebooks and iPads, can still be imported by CSV or created through the REST API, and every other feature treats them identically.
Do you support outbound webhooks?
Not yet. The REST API is request-based, so integrations poll rather than being pushed to. For event-driven automation today, Zapier is the practical route.
What can I do with the API that I cannot do in the interface?
Nothing — that is deliberate. The API covers the same ground as the interface and enforces the same permissions, so an API key can never reach further than the person it belongs to. The point is automation, not elevated access.
Is the API available on the free plan?
API access is a paid-plan feature. The integrations themselves — Entra/Intune, LogMeIn, Zapier and email-to-ticket — are also paid-plan features. The free plan covers the core help desk and knowledge base.
How do I revoke access if a key leaks?
Void that specific key. Keys are individually named and revocable, so retiring one does not disturb any other integration, and the request log shows exactly what it was used for beforehand.