TeamViewer
Helpdesk & ITSMManage TeamViewer remote access from AI agents. Agents keep the Computers & Contacts list organized, provision and offboard company users, and open remote-control service cases with shareable supporter and customer links straight from a helpdesk ticket.
What This Integration Enables
Remote access is the most sensitive capability in the support stack. A TeamViewer session is control of someone else's machine, and the account that grants it is an inventory of every computer your team can reach. FlowRunner treats that inventory as something agents maintain and something humans authorize: agents keep the Computers & Contacts list accurate, provision and audit company users, and open service cases from real tickets, while the moment a connection link is minted stays under a person's control. - Open remote-control service cases directly from helpdesk tickets, with supporter and end-customer links routed through the channels you already use - Keep devices, contacts, and groups organized so the list reflects your actual fleet - Provision company users from HR or identity events instead of a spreadsheet checklist - Sweep devices, users, and open sessions on a schedule for asset and access audits
Without FlowRunner
With FlowRunner
Use Case Scenarios
From ticket to session without the phone tag
A customer files a ticket in [Zendesk](/integrations/zendesk) that needs hands-on help. The agent pulls the ticket context, calls Create Session in the right support group, and replies to the customer with the end-customer link while the supporter link posts to the technician's [Slack](/integrations/slack) channel. The customer clicks, the technician connects, and nobody spends twenty minutes reading a nine-digit ID over the phone. When a PagerDuty incident fires on a managed host instead, the same pattern opens the case and hands the links to the on-call engineer.
Offboarding that actually closes access
HR marks an employee as departed in the identity system. The agent calls List Users to find the matching TeamViewer account, List Devices and List Contacts to find entries the person owned, and assembles a decommission summary: one user account, two managed laptops, one contact entry. An IT lead approves the plan, and the agent executes it, moving devices to a recovery group with Update Device and removing stale entries with Remove Device. The same flow in reverse runs onboarding: Create User provisions the account with the permission set the role calls for, not whatever the last hire happened to get.
The fleet audit that runs itself
Every Monday the agent calls List Devices, List Groups, List Users, and List Sessions, and appends the results to [Google Sheets](/integrations/google-sheets). It compares the device list against the asset inventory, flags machines that have not been online in 30 days, and posts a digest of unassigned devices and still-open service cases. The quarterly access review becomes a read of a living document instead of a scramble.
Human-in-Loop Highlight
Create Session mints two working links: one that lets a supporter take control of a machine, and one that reaches the customer and invites them to grant it. Once the end-customer link is delivered, you cannot recall it from their inbox. So FlowRunner agents prepare the session but do not release it. The technician sees: "Ticket 4821 requests remote help. Target device LAPTOP-MFG-07 is online. Session ready in group Field Support. Send links?" A person confirms the requester is who the ticket says they are, then the links go out. The [human-in-the-loop](/concepts/human-in-the-loop) gate sits exactly where remote access becomes real.
Agent Capabilities
13 actionsDevices
3- List Devices Lists all managed devices in the account's Computers & Contacts list with device ID, TeamViewer ID, alias, online state, group assignment, and remote-control availability. The lookup step behind every device workflow.
- Update Device Updates a managed device's alias, description, or group assignment. Only supplied fields change, so enrichment passes leave everything else untouched.
- Remove Device Removes a managed device from the Computers & Contacts list. It does not uninstall TeamViewer on the remote machine, which makes it the right tool for list hygiene rather than decommissioning.
Groups
3- List Groups Lists all groups including those shared with the account, with ID, name, owner, permission level, and sharing details.
- Create Group Creates a new group for organizing devices and contacts. Used when onboarding a new team, region, or client fleet.
- Delete Group Deletes a group. Devices and contacts inside it are not deleted, they become ungrouped, so cleanup flows re-home them first.
Users
3- List Users Lists company user accounts with ID, name, email, and active state. The roll call behind access audits and offboarding sweeps.
- Get User Retrieves a single user's name, email, permissions, active state, and account settings. Used to verify what a specific account can actually do.
- Create User Creates a new company user with name, email, initial password, and an explicit permission set. The provisioning step that turns an HR event into an account.
Contacts and Account
2- List Contacts Lists the people, as opposed to managed computers, in the Computers & Contacts list, with contact ID, name, group, and online state.
- Get Account Returns the account the script token authenticates as, including name, email, and user ID. The sanity check that a workflow is acting as the account you think it is.
Sessions
2- List Sessions Lists remote-control service cases with session code, state, group, assignee, description, and timestamps. The audit view over who is connecting where.
- Create Session Creates a new remote-control service case and returns the supporter and end-customer connection links. The operation this page's human gate exists for.
Frequently Asked Questions
What can FlowRunner do with TeamViewer?
FlowRunner agents can run List Devices, Update Device, and Remove Device in TeamViewer, plus 10 more actions.
Does connecting TeamViewer to FlowRunner require OAuth?
No. TeamViewer connects to FlowRunner with an API key, no OAuth flow required.
Can TeamViewer trigger a FlowRunner workflow automatically?
TeamViewer doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with TeamViewer
$100 in credits. No card required. Connect in minutes.