Resources · Make integration

Teamup Make integrationAutomate Teamup with Make.

Your Teamup calendar can update itself when the rest of your stack moves. The Teamup Make integration gives you 14 modules: 3 triggers, 9 actions and 2 searches. This guide is for people who already run their team schedule in Teamup and want to connect it, then build a first working scenario.

Try the Teamup integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Teamup Make integration do for you?

The Teamup Make integration links your Teamup calendar to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick of that chain, such as a trigger that watches Teamup or an action that writes an event. You pick the bricks, Make runs them for you.

A kickoff slot for every new project. Watch Sub-Calendars notices when someone adds a sub-calendar, and Create an Event drops a first meeting into your calendar, so no project starts without a date on the board.

Changes that reach the right people. Watch Events Updated picks up events that were edited. Pass them to a chat or email module from another app and your field team hears about a moved appointment without refreshing the calendar.

A tidy calendar after a project closes. Search Events finds the events you target, then Delete an Event or Delete a Sub-Calendar clears what no longer belongs there. Test that one carefully before you switch it on.

What the listed modules do not cover, Make an API Call can reach with the same connection. The Teamup documentation in Make flags its own content as AI-generated, so check important details against Teamup. If you are still choosing a platform, the n8n vs Make page sets out the criteria, and the Make pricing page explains how operations are counted. Scheduling is also central to the Acuity Scheduling Make integration.

Connect

How do you connect your Teamup account to Make?

  1. 01

    Get an API key from Teamup

    In Teamup, open Settings, then Integrations, API Integration and Manage Applications. Create a new application and copy the API key shown on screen. Teamup asks you to apply for API credentials first, so start there.

  2. 02

    Add a Teamup module in your scenario

    In Make, place any Teamup module in your scenario and click Create a connection. A connection is your Teamup account linked to Make once, then reused by every Teamup module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you manage several calendars. Paste the credentials you copied from Teamup, or follow the instructions on screen, then save.

First scenario

Build your first scenario with Teamup

GoalWhen a new sub-calendar appears in Teamup, Make books a kickoff event in your calendar.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. That opens the list where you choose the first module, the one that starts everything.

  2. 02

    Add Watch Sub-Calendars

    Search for Teamup, pick Watch Sub-Calendars and select your connection, or click Create a connection if this is your first Teamup module in Make.

  3. 03

    Add Create an Event

    Click the + on the right of the trigger and add Create an Event. Choose the calendar Make lists for you, then map data from the trigger into the event so each kickoff mentions its project.

  4. 04

    Test with Run once

    Add a test sub-calendar in Teamup, then click Run once. Open the bubble above each module to read the bundles it received, a bundle being one item passed along, here one sub-calendar.

  5. 05

    Schedule and switch it on

    Click the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Keep it or change it, then switch the scenario on.

Triggers

What can start a Teamup scenario?

3 modules start a scenario when something happens in Teamup. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Teamup as soon as it happens.

Teamup1Watch Events

Watch Events

Scheduled trigger

In Make“Watches for new events.”

Watch Events hands your scenario each event that is newly added in Teamup, one bundle per event, so the next modules can act on bookings as they land in the calendar.

How it fires
scheduled. Make checks Teamup on the scenario's schedule, which you see as the clock badge on the module, so an event shows up at the next check rather than the second it is created.
When to use it
a new site visit or shift is added and you want it copied to a sheet or announced in chat.
Watch out
edits to existing events are ignored here; that job belongs to Watch Events Updated.
Teamup2Watch Events Updated

Watch Events Updated

Scheduled trigger

In Make“Watches for new or updated events.”

With Watch Events Updated, you catch both fresh events and the ones someone changed, which keeps anything downstream in step with the current version of the calendar.

How it fires
scheduled. Make checks Teamup on the scenario's schedule and passes on whatever is new or edited since its last look.
When to use it
a client meeting moves and the people involved need to hear the new time without opening Teamup.
Watch out
since new events come through too, pair it with Watch Events in the same scenario and you would handle them twice. Choose one of the two.
Teamup3Watch Sub-Calendars

Watch Sub-Calendars

Scheduled trigger

In Make“Watches for new sub-calendars.”

This trigger tells you when a sub-calendar is born, which makes it the natural starting point for setup work around a new team, room or project inside Teamup.

How it fires
scheduled. Make checks Teamup on the scenario's schedule, so a new sub-calendar is picked up at the following check.
When to use it
each project gets its own sub-calendar and you want a kickoff event, a folder or a note created in the same move.
Watch out
it reacts to new sub-calendars only; renaming one does not start the scenario.
Modules

Every Teamup module in Make, and when to reach for it

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

Teamup1

Create an Event

Action

In Make“Creates a new event in the specified calendar.”

Puts a new event on the calendar you specify, so a booking made elsewhere lands in Teamup without anyone retyping it.

When to use it
a form reply or a signed quote should become a dated slot that the whole team can see.
Watch out
if the same scenario watches new events on that calendar, you can end up in a loop.
Teamup2

Create a Sub-Calendar

Action

In Make“Creates a new sub-calendar.”

Adds a sub-calendar to your Teamup setup, giving a new team, room or client its own lane with no manual setup in the settings.

When to use it
a new project is opened in your CRM or tracker and deserves a dedicated space in the calendar.
Watch out
run it once per project, or duplicates will pile up quickly.
Teamup3

Delete an Event

Action

In Make“Deletes an event.”

Removes one event from Teamup, which keeps the calendar honest when a booking is cancelled somewhere else in your tools.

When to use it
an order is refunded or an appointment is dropped in another app, and the slot should free up.
Watch out
check which event the scenario targets, and try it on a dummy event first.
Teamup4

Delete a Sub-Calendar

Action

In Make“Deletes a sub-calendar.”

Takes an entire sub-calendar out of Teamup, handy for clearing away a finished project instead of leaving it cluttering the view.

When to use it
a project is marked closed in your tracker and its lane has no reason to stay.
Watch out
this is the heaviest action in the list; point it at the right sub-calendar and try it on a test one.
Teamup5

Get an Event

Action

In Make“Retrieves a specific event.”

Fetches the full details of one event you already know, so later modules can use its current data rather than a stale copy.

When to use it
you stored an event reference in a sheet and need the latest version before sending a reminder.
Watch out
it needs one precise event; to look for several, use Search Events.
Teamup6

Get a Sub-Calendar

Action

In Make“Retrieves a specific sub-calendar.”

Returns the details of a single sub-calendar, giving the rest of the scenario something reliable to map from when it names or routes things.

When to use it
an event arrives and you want the name of its sub-calendar in a message or a report row.
Watch out
it reads one sub-calendar; for all of them, List Sub-Calendars is the right module.
Teamup7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Teamup API to your scenario, reusing the connection you already built, for the cases no ready-made module handles.

When to use it
you need an endpoint that none of the ready-made Teamup modules covers.
Watch out
you write the request yourself, so keep the Teamup API documentation open and test with Run once before going live.
Teamup8

Update an Event

Action

In Make“Updates an event.”

Changes an event that already exists, so a new time or a new detail decided in another tool shows up in Teamup on its own.

When to use it
a client reschedules through your booking form and the team calendar should follow.
Watch out
you need to know which event to edit; Search Events usually runs just before it.
Teamup9

Update a Sub-Calendar

Action

In Make“Updates a sub-calendar.”

Edits a sub-calendar in place, which lets a renamed project or team carry its new label into Teamup without a trip to the settings.

When to use it
a project gets its final name in your CRM and the calendar lane should match.
Watch out
Watch Sub-Calendars will not notice this change, as it only sees new ones.
Teamup10

List Sub-Calendars

Search

In Make“Retrieves a list of sub-calendars.”

Brings back every sub-calendar in your Teamup calendar as separate bundles, which is the easy way to act on all of them in turn.

When to use it
you want an inventory of teams or rooms in a sheet, or a check across all lanes.
Watch out
each sub-calendar costs the next modules one operation, a single run of a module, so filter early.
Teamup11

Search Events

Search

In Make“Searches for events or list them all.”

Finds the events that match what you ask for, or lists them all, and returns zero, one or many results for the modules that follow.

When to use it
before an update or a deletion, to locate the exact events concerned.
Watch out
zero results is a possible answer, so plan what the scenario should do when nothing matches.
Need help

Need help automating Teamup with Make?

A person reads every message.

FAQ

Teamup and Make: common questions

01Is the Teamup Make integration free?
Yes, as far as Make is concerned. Teamup is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and raise execution time to 40 minutes. Your Teamup subscription is a separate matter, covered on the Teamup pricing page, and you do need an active Teamup account for the connection to work.
02What do you need to connect Teamup to Make?
An active Teamup account and API credentials. Teamup asks you to apply for them through its Integrations page. Once that is done, go to Settings, Integrations, API Integration, then Manage Applications, create a new application and copy the API key. In Make, add a Teamup module, click Create a connection, optionally give it a name, and paste the key. The same connection then serves all 14 Teamup modules in any scenario you build.
03Does the Teamup trigger react in real time?
No. All 3 Teamup triggers are scheduled: Make checks Teamup on the scenario's schedule rather than being told the moment something changes. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. On a paid plan the gap can drop to 1 minute. For most calendar work, like announcing a new booking or a moved meeting, a short delay is fine. If you need tighter timing, a paid plan is the lever.
04What if a Teamup module you need is missing in Make?
Use Make an API Call. It sends any request the Teamup API accepts, with the connection you already set up, so you are not limited to the ready-made modules. You write the request yourself, which means reading the Teamup API documentation. Also keep in mind that the Teamup page in the Make documentation is marked as AI-generated and may contain mistakes, so confirm important behavior with Teamup directly before you rely on it in a live scenario.
05Should you use Make or n8n for Teamup?
It depends on your criteria. In Make, Teamup comes with 14 modules covering events and sub-calendars, 3 scheduled triggers, and Make an API Call for anything else, all usable from the Free plan. The same app often has an n8n node too, so check what that node covers before deciding. Compare the actions each tool offers for your exact case and how you prefer to build, rather than assuming one fits every team.
Same platform

Other docs you might need on this stack.

Browse all integrations