Resources · Make integration

TeamViewer Make integrationAutomate TeamViewer with Make.

Tired of adding every new teammate to TeamViewer by hand? The TeamViewer Make integration gives you 23 modules: 17 actions and 6 searches over users, groups, devices, contacts and meetings. This guide is for IT and support leads, and it walks you from connection to a first working scenario.

Try the TeamViewer integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TeamViewer Make integration do for you?

The TeamViewer Make integration links your TeamViewer account to Make, a tool where you build a scenario (an automation made of connected steps) without writing code. Each step is a module, one brick that creates, reads, updates or searches something. Here, those bricks work on TeamViewer users, groups, devices, contacts and meetings.

Onboard a new technician without the admin console. When a hire shows up in your HR tool or a spreadsheet, Create a User opens their TeamViewer account without anyone logging in to do it. When someone leaves, Update a User is where the offboarding step lives.

Book a support session the moment a ticket asks for one. Your helpdesk or form app starts the scenario, Create a Contact saves the customer in TeamViewer, and Create a Meeting sets up the session. If the ticket is cancelled, Delete a Meeting removes it.

Keep an inventory you can actually read. Search Devices and Search Users pull lists out of TeamViewer so another module can write them into a sheet, for example an Airtable Make integration base.

One thing to know up front: TeamViewer has no trigger in Make, so it never starts a scenario by itself. Something else does, another app or the schedule of the scenario. And the official doc for this app is flagged as AI-generated, so check important details on the TeamViewer side.

The same app often exists as a node in n8n too; the n8n vs Make comparison lays out how the two tools differ. If you would rather learn the editor step by step, the Make training covers it.

Connect

How do you connect TeamViewer to Make?

  1. 01

    Get your TeamViewer access ready

    You need an active TeamViewer account and an API token. In the advanced setup, you create an app from Edit profile, tab Apps, then Create App, and copy the Client ID and Client secret it shows.

  2. 02

    Add a TeamViewer module

    Inside your scenario, add any TeamViewer module and click Create a connection. The Connection name field is optional, but a clear name helps once you run several accounts side by side.

  3. 03

    Paste your credentials

    Enter the credentials you copied from TeamViewer, or follow the instructions on screen. That connection (your account linked to Make once) is then reused by every TeamViewer module you add.

First scenario

Your first scenario: a TeamViewer session for every new client

GoalWhen a new client lands in another app, Make adds them to TeamViewer as a contact and books a meeting.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where new clients appear (your form, CRM or sheet) and the module that spots a new entry.

  2. 02

    Add Create a Contact

    Click the + on the right, search for TeamViewer and choose Create a Contact. Click Create a connection if it is your first TeamViewer module, then map the client's details from the first module.

  3. 03

    Chain Create a Meeting

    Add one more module, Create a Meeting, on the same connection. Fill its fields with data mapped from the earlier modules, so each new client gets their own session.

  4. 04

    Test with Run once

    Add a test client in your source app and click Run once. Open each module's bubble to read the bundle (one item passed along) it received, and check the new contact and meeting in TeamViewer.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule; a new scenario runs every 15 minutes by default. Then switch the scenario on. Every module run counts as one operation on your Make plan.

Modules

What the TeamViewer modules do

TeamViewer gives you 23 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

TeamViewer1

Check the API status

Action

In Make“Checks the API status.”

This module asks TeamViewer whether its API answers, so you know the link is alive before the real work starts.

When to use it
place it at the start of a scenario you just built, or while you chase an error, to rule out a broken connection first.
Watch out
a positive answer says the API is reachable, nothing more, so still test the real modules with Run once.
TeamViewer2

Create a Contact

Action

In Make“Creates a new contact.”

Adds a new entry to your TeamViewer contacts, which saves someone from typing it in when a customer or partner first shows up elsewhere.

When to use it
right after a form, CRM or helpdesk module delivers a new person you will support remotely.
Watch out
run Search Contacts first if the same person can come in twice, or you will end up with duplicates.
TeamViewer3

Create a Device

Action

In Make“Creates a new device.”

Registers a new device in your TeamViewer list, so a freshly issued laptop is visible to your support team from day one.

When to use it
when your asset sheet or procurement tool records a machine being handed to someone.
Watch out
the fields show up once the connection exists, so open the module in the editor and see what TeamViewer asks for before you map anything.
TeamViewer4

Create a Group

Action

In Make“Creates a new group.”

Opens a new group in TeamViewer, a clean place to sort the devices or contacts that belong together, such as one client or one site.

When to use it
when a new client account is signed in your CRM and you want their machines kept apart from the rest.
Watch out
a scenario that runs again on the same record creates a second group, so add Search Groups before it.
TeamViewer5

Create a Meeting

Action

In Make“Creates a new meeting.”

Sets up a new TeamViewer meeting from data your scenario already holds, so nobody has to open TeamViewer to book the session.

When to use it
a ticket, booking or form entry calls for a live session with a customer or a colleague.
Watch out
the meeting details come from earlier modules, so test with Run once and read the result before you switch the scenario on.
TeamViewer6

Create a User

Action

In Make“Creates a new user.”

Opens a TeamViewer account for a new person in your company, which turns onboarding into one step fired by the tool where hires are recorded.

When to use it
a new technician or agent appears in your HR app or staff sheet.
Watch out
if the same hire can reach the scenario twice, run Search Users first so nobody ends up with two accounts.
TeamViewer7

Delete a Contact

Action

In Make“Deletes an existing contact.”

Removes a contact from TeamViewer, keeping your list limited to the people you still support.

When to use it
a customer closes their account in your CRM, or a partnership ends and their record goes with it.
Watch out
a deletion cannot be undone from Make; feed it one exact contact, and if Search Contacts finds it, check with Run once that the search returns that person only.
TeamViewer8

Delete a Device

Action

In Make“Deletes an existing device.”

Takes a device off your TeamViewer list, so retired or returned machines stop showing up next to the live ones.

When to use it
your asset tracker marks a laptop as returned, lost or recycled.
Watch out
there is no undo. Test on a spare device with Run once, and make sure a search that returns several bundles does not wipe more than you meant.
TeamViewer9

Delete a Group

Action

In Make“Deletes an existing group.”

Deletes a whole group in TeamViewer, which tidies up once a client or project is finished and its folder is no longer useful.

When to use it
a contract ends in your CRM and the matching group should go too.
Watch out
this is permanent, so read the group with Get a Group first and confirm it is the right one before it runs.
TeamViewer10

Delete a Meeting

Action

In Make“Deletes an existing meeting.”

Cancels a scheduled TeamViewer meeting by removing it, so a session that no longer makes sense disappears without a manual check.

When to use it
a ticket is closed or a booking is cancelled before the session takes place.
Watch out
the meeting is gone for good; map the exact meeting you created earlier rather than one picked from a search.
TeamViewer11

Get a Group

Action

In Make“Retrieves an existing group.”

Reads one existing group and hands its details to the next module, which is handy when you need to know what a group looks like before changing it.

When to use it
before Update a Group or Delete a Group, to check you are about to touch the right one.
Watch out
it returns a single group; to find one by name, start with Search Groups.
TeamViewer12

Get a Meeting

Action

In Make“Retrieves an existing meeting.”

Fetches the details of one meeting you already know, so a later step can reuse them, for instance in a reminder message sent through another app.

When to use it
after a meeting was created and you need its information again further down the scenario.
Watch out
it reads one meeting only; when you do not know which one, start with Search Meetings and pick from its bundles.
TeamViewer13

Get a User

Action

In Make“Retrieves an existing user.”

Retrieves one TeamViewer user and passes their details on, so the scenario works with the account as it is right now.

When to use it
an HR change arrives and you want to look at the current account before running Update a User.
Watch out
it expects one specific user; if you only have a name or an email, go through Search Users first.
TeamViewer14

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the TeamViewer API from your scenario, reusing the same connection, when none of the ready-made modules does what you need.

When to use it
the action you want exists in the TeamViewer API but has no ready-made module in Make.
Watch out
you write the request yourself, so keep the TeamViewer API documentation open while you set it up.
TeamViewer15

Update a Group

Action

In Make“Updates an existing group.”

Changes an existing group, which keeps TeamViewer in line when a client or team is renamed in the tool you treat as the reference.

When to use it
a company name or project label changes in your CRM and the group should follow.
Watch out
point it at one exact group; Get a Group or Search Groups are the usual way to find it.
TeamViewer16

Update a Meeting

Action

In Make“Updates an existing meeting.”

Edits a meeting that already exists, so a rescheduled session stays correct in TeamViewer without anyone reopening it.

When to use it
a customer moves their booking in your scheduling app and the TeamViewer session should match.
Watch out
you need the meeting you created earlier; write its details into a sheet when Create a Meeting runs.
TeamViewer17

Update a User

Action

In Make“Updates an existing user.”

Modifies an existing TeamViewer account, which makes role changes and departures a matter of one scenario instead of a trip to the admin console.

When to use it
someone changes team, or leaves, and your HR tool records it.
Watch out
run Get a User or Search Users first so the update lands on the right person and not on a namesake.
TeamViewer18

Search Contacts

Search

In Make“Searches for contacts or lists them all.”

Looks through your TeamViewer contacts, or lists them all, and returns each match as its own bundle for the following modules.

When to use it
before Create a Contact, to check whether the person is already there, or to export your contact list into a sheet.
Watch out
it can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations.
TeamViewer19

Search Devices

Search

In Make“Searches for devices or lists them all.”

Pulls the devices from your TeamViewer account, all of them or the ones matching your search, which gives you the raw material for an inventory.

When to use it
you want a sheet or database listing every machine your team can reach.
Watch out
a long device list means many bundles and many operations downstream; narrow the search when you only need a few.
TeamViewer20

Search Groups

Search

In Make“Searches for groups or lists them all.”

Finds groups in TeamViewer, or lists every group, so the scenario can work out which one a client or site belongs to.

When to use it
ahead of Create a Group to avoid a duplicate, or ahead of Update a Group when you only know the name.
Watch out
a vague name can match several groups, and each match flows on as its own bundle, so check the result with Run once.
TeamViewer21

Search Meetings

Search

In Make“Searches for meetings or lists them all.”

Returns your TeamViewer meetings, filtered or complete, so you can see what is booked without opening the app.

When to use it
you want to copy upcoming sessions into a shared calendar sheet, or spot one to update after a change.
Watch out
each meeting found becomes a separate bundle, and a delete or update module placed after it acts on every single one.
TeamViewer22

Search Users

Search

In Make“Searches for users or lists them all.”

Lists the users of your TeamViewer account or finds the ones that match, which is the starting point for an access review.

When to use it
you compare TeamViewer accounts with your staff list to catch people who left.
Watch out
search before any Update a User in a loop, and check the bundles with Run once so a broad match does not touch the whole team.
TeamViewer23

Update a Device

Search

In Make“Updates an existing device.”

Changes the details of a device already in TeamViewer, so your remote access list reflects what your asset records say.

When to use it
a laptop is reassigned to someone else or moved to another site in your tracking sheet.
Watch out
Make files this module under searches rather than actions; treat it as an edit all the same and feed it the exact device.
Need help

Need help automating TeamViewer with Make?

A person reads every message.

FAQ

Questions people ask about TeamViewer and Make

01Is the TeamViewer Make integration free?
Yes, on the Make side. TeamViewer is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, and stops a run after 5 minutes. Paid plans go down to 1 minute between runs and allow 40 minutes per run. Usage is counted in operations, one per module run. You still need your own TeamViewer account and an API token, which follow TeamViewer's own subscription terms.
02What do you need to connect TeamViewer to Make?
An active TeamViewer account and an API token. You add a TeamViewer module, click Create a connection, optionally name it, then enter the credentials copied from TeamViewer or follow the on-screen steps. For the advanced setup, you create an app in TeamViewer from Edit profile, then the Apps tab and Create App, set the callback URI that Make's doc gives, grant permissions for Session, account and connection reports, and copy the Client ID and Client secret.
03Can TeamViewer start a Make scenario in real time?
No. TeamViewer has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario by itself. You start the scenario from another app, for example a helpdesk, form or CRM module that notices a new entry, or you run it on the schedule of the first module, every 15 minutes by default. The TeamViewer modules then act as later steps: they create, read, update or search what that first module hands them.
04What if a TeamViewer module you need is missing?
Use Make an API Call. It reaches any endpoint of the TeamViewer API with the connection you already set up, so you are not limited to the 23 listed modules. You do write the request yourself, so keep the TeamViewer API documentation at hand. Also note that the Make doc for this app is marked as AI-generated and may contain mistakes, so confirm important behaviour with TeamViewer directly before you rely on it.
05Should you use Make or n8n for TeamViewer?
It depends on the tool your team already knows. In Make, TeamViewer comes with 23 modules covering users, groups, devices, contacts and meetings, plus Make an API Call for the rest, and no trigger. The same app often has an n8n node as well. Before choosing, check that the actions you need exist in each tool, and compare the two with your own scenario rather than with a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations