--- title: "TeamViewer Integration" description: "Manage 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." url: https://flowrunner.ai/integrations/teamviewer date_modified: 2026-08-01T02:40:32-07:00 --- # TeamViewer [Helpdesk & ITSM](https://flowrunner.ai/integrations/category/helpdesk-itsm) Manage 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. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 13 actions · API key · available [TeamViewer website](https://teamviewer.com/) · [Platform Documentation](https://www.teamviewer.com/en/for-developers/) · Capability data verified 2026-07-28 1. A hands-on support request lands in the helpdesk queue, tagged for remote assistance 2. List Devices looks up the caller's managed computer by alias and checks whether it is online 3. List Users confirms the assigned technician holds an active company account before any session is provisioned 4. Create Session opens a remote-control service case in the correct support group with the ticket summary as its description 5. The technician reviews the ticket and the target device and confirms the session should go out before any connection link leaves the building 6. The supporter link goes to the technician and the end-customer link goes back to the requester through the helpdesk reply 7. List Sessions runs at end of day and logs each case's state and assignee to the audit sheet ## 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 **Inventory drift**: The Computers & Contacts list accumulates dead machines, duplicate entries, and devices nobody can name **Offboarding gaps**: A departed employee's account stays active because deactivation lives on a manual checklist someone forgot **Session sprawl**: Remote-control cases open ad hoc from personal accounts, with no record of who connected to which machine ### With FlowRunner **A list that matches reality**: Agents reconcile devices and groups against your asset inventory on a schedule and flag what does not belong **Provisioning tied to identity events**: User accounts are created from HR system events with permissions assigned deliberately, and audited the same way **Sessions with a paper trail**: Every service case starts from a ticket, links are delivered through the helpdesk, and open sessions are swept daily ## Use Case Scenarios ### From ticket to session without the phone tag A customer files a ticket in [Zendesk](https://flowrunner.ai/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](https://flowrunner.ai/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](https://flowrunner.ai/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](https://flowrunner.ai/concepts/human-in-the-loop) gate sits exactly where remote access becomes real. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 13 actions ### Devices 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. **Work at TeamViewer?** This integration exposes TeamViewer to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/teamviewer. Site index: https://flowrunner.ai/llms.txt