TeamViewer

On this page

The TeamViewer integration lets technicians start a TeamViewer remote session from an Incident. It is supplied as workflow configuration, not built into the product: two actions on Incidents and three parameters that turn them on. How workflow actions work in general is described in Workflow Overview.

What the integration includes

A new 2026.1 database created with the Default Workflow contains the TeamViewer integration described on this page. An upgraded database need not contain it, and an administrator may have changed it. See Default Workflow Configuration.

  • The action TeamViewer Invite e-mails the Incident's requester an invitation that carries a session code and a join button.
  • The action TeamViewer Connect opens the session once the requester has authorized it.
  • Both actions belong to the Integrations action group.
  • The parameters TeamViewer Status, TeamViewer Script Token, and TeamViewer Group Number turn the integration on and connect it to your TeamViewer group.
  • The integration has no scheduled task.

The integration ships switched off: TeamViewer Status is set to Disabled in the supplied configuration. Until an administrator enters the TeamViewer credentials and enables the integration, it makes no call to TeamViewer.

The supplied configuration sets no deployment condition on the integration: it is the same on premises and in Alloy Navigator Cloud.

The two actions are shown on Incidents only while TeamViewer Status is Enabled and both TeamViewer Script Token and TeamViewer Group Number are filled in. On a system where the integration is not configured, the actions are not shown.

The integration creates each session through the TeamViewer sessions API at webapi.teamviewer.com. It authenticates with the script token and creates the session in the group that the group number identifies.

Configure the integration

The three parameters are on the integration's page in the Workflow Configuration tree, the category Integrations > TeamViewer. Workflow Configuration, where parameter values are set, is part of the product; the TeamViewer category and its parameters come from the supplied configuration. The page exists in both the Settings App and the Admin Center.

Parameter What it sets
TeamViewer Status Enabled or Disabled. When enabled, the integration requires the script token and the group number.
TeamViewer Script Token The script token you create in the TeamViewer Management Console.
TeamViewer Group Number The 9-digit Group Number associated with your TeamViewer group. It appears in the group's URL.

The script token is stored as a workflow parameter value, not with your accounts or mail profiles. In the supplied configuration, TeamViewer Script Token is a plain-text parameter, not an encrypted one. Treat an exported workflow file as sensitive: the plain-text values in it are readable.

In the Settings App

Before you begin: you need the administrative right that allows managing Workflow Configuration. See Permissions Reference.

  1. Under Workflow and Business Logic, open Workflow Configuration.
  2. In the category tree on the left, select Integrations > TeamViewer. The right pane shows one input control for each parameter, with its description.
  3. Enter the TeamViewer Script Token and the TeamViewer Group Number, and set TeamViewer Status to Enabled.
  4. Save your changes. Only the changed values of the selected category are saved.

In the Admin Center

Before you begin: you need the Workflow Configuration permission. See Permissions Reference.

  1. Under Workflow and Business Logic, open Workflow Configuration.
  2. In the category tree, open Integrations > TeamViewer. The page shows one control for each parameter.
  3. Enter the TeamViewer Script Token and the TeamViewer Group Number, and set TeamViewer Status to Enabled. Save and Cancel appear once you change a value.
  4. Click Save.

The Admin Center does not check the values you enter against the parameter's type or declared validation rules. If you leave the page with unsaved changes, the Admin Center asks "You should save you changes before leaving this page. Do you want to leave this page?"

What technicians see on Incidents

Technicians run the two actions on an Incident.

  • TeamViewer Connect is not hidden before an invitation is sent. If it runs while no session is stored for the Incident, a workflow message tells the technician to run TeamViewer Invite first, and the action stops.
  • Each Incident keeps one TeamViewer session. Running TeamViewer Invite again replaces the stored session, and TeamViewer Connect then opens the new session.
  • In the Web App, TeamViewer Connect opens the session on the technician's own computer.