TeamViewer

• New deviceRuns for each new device in TeamViewer. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.
• New or updated deviceRuns for each device added or changed in TeamViewer. Ones already there when the workflow is turned on start it only when they change. It can watch up to 4,000. How often it checks follows your workspace plan.
• New contactRuns for each new contact in TeamViewer. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.
• New or updated contactRuns for each contact added or changed in TeamViewer. Ones already there when the workflow is turned on start it only when they change. It can watch up to 4,000. How often it checks follows your workspace plan.
• New groupRuns for each new group in TeamViewer. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.
• New or updated groupRuns for each group added or changed in TeamViewer. Ones already there when the workflow is turned on start it only when they change. It can watch up to 4,000. How often it checks follows your workspace plan.
• New sessionRuns for each new session in TeamViewer. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.
• New or updated sessionRuns for each session added or changed in TeamViewer. Ones already there when the workflow is turned on start it only when they change. It can watch up to 4,000. How often it checks follows your workspace plan.
• New userRuns for each new user in TeamViewer. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.
• New or updated userRuns for each user added or changed in TeamViewer. Ones already there when the workflow is turned on start it only when they change. It can watch up to 4,000. How often it checks follows your workspace plan.
• New connection reportRuns for each new connection report in TeamViewer. Ones already there when the workflow is turned on don't start it. It can watch up to 4,000. How often it checks follows your workspace plan.

• Get accountReturns the account.
• List devicesGET api/v1/devices.
• Get deviceGET api/v1/devices/{id}.
• Update devicePUT api/v1/Devices/{id}.
• List contactsRetrieves all contacts with optional filtering.
• Get contactRetrieves a specific contact by ID.
• List groupsReturns groups by filter criteria.
• Get groupReturns group by groupId.
• Create groupCreates a group.
• Update groupUpdates group.
• Delete groupDeletes a group.
• List support sessionsGET api/v1/Sessions.
• Get support sessionGET api/v1/Sessions/{id}.
• Create support sessionPOST api/v1/Sessions.
• Update support sessionPUT api/v1/Sessions/{id}.
• Delete support sessionDELETE api/v1/Sessions/{id}.
• List usersReturns users with filter criteria.
• Get userReturns a user.
• List connection reportsReturns the session reports, the number of remaining reports and a link to request the further reports if the remaining number is > 0. All parameters are nullable, i.e. optional. We detect the type of the token implicitly by getting AccountId and CompanyId out of the token. In the backend, we filter the reports depending on which value is set. Only one of these values must and may be set. Reports are sorted by end date descending, i.e. newest sessions first. With each call, at most 1000 session reports are returned. GET api/v1/reports/connections .
• Get connection reportGET api/v1/reports/connections/{id:Guid}.

No actions match that.