Resources · Make integration

Tidycal Make integrationAutomate Tidycal with Make.

Every Tidycal booking can start work in your other tools. The Tidycal Make integration gives you 3 triggers and one API call module. This guide shows how to link your account, build a first scenario and pick the right trigger.

Try the Tidycal integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Tidycal Make integration let you automate?

The Tidycal Make integration links your Tidycal account to Make so that bookings and contacts can feed other apps without code. In Make you build a scenario, the automation itself, from modules: each module is one brick, such as a trigger that watches Tidycal or an action that sends data somewhere else.

A booking log that fills itself. Watch New Booking picks up each fresh appointment, and the next module writes it into the sheet or CRM your team already uses. Nobody copies calendar details by hand anymore.

A clean follow-up when someone cancels. Watch Booking Canceled notices the cancellation, so your scenario can update the deal, warn the account owner or send a new booking link through another app.

A contact list that stays in sync. Watch New Contact sends every person Tidycal records to your mailing tool, ready for the right sequence.

Keep the limits in mind: all three Tidycal triggers are scheduled, which means Make checks for news on the scenario's schedule rather than hearing about it the moment it happens. Tidycal has no dedicated action for creating or editing bookings in Make; the Make an API Call module is the route when you need an endpoint the triggers do not cover. If you are still weighing tools, the n8n vs Make comparison lays out both options, and the Make review covers the platform as a whole. Running several scheduling tools? The Acuity Scheduling Make integration follows the same logic.

Connect

How do you connect Tidycal to Make?

  1. 01

    Add a Tidycal module

    Log in to Make, open your scenario and add any Tidycal module, for example Watch New Booking. In the module panel, click Create a connection. A connection is your Tidycal account linked to Make once, then reused by every Tidycal module.

  2. 02

    Name it and save

    The Connection name field is optional, but a clear label helps when several people share the workspace. You only open Show advanced settings if you use your own Tidycal app credentials. Then click Save.

  3. 03

    Approve access in Tidycal

    If Tidycal asks you to sign in, log in with the account that owns the bookings and confirm access. Back in Make, the connection appears in the module and the fields can be filled.

First scenario

Your first scenario: act on each new Tidycal booking through the API

GoalWhen someone books a slot in Tidycal, Make sends a request of your choice to the Tidycal API with that booking.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the large + in the middle of the editor. This first module is the one that starts everything.

  2. 02

    Pick Watch New Booking

    Search for Tidycal, choose Watch New Booking and select the connection you made earlier, or click Create a connection if this is your first Tidycal module.

  3. 03

    Add Make an API Call

    Click the + on the right of Watch New Booking and add Make an API Call, which reuses the same connection. Pick the endpoint in the Tidycal API documentation and map the booking data into the request.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one booking.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. New bookings now reach the API without you.

Triggers

Tidycal triggers in Make

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

Tidycal1Watch New Booking

Watch New Booking

Scheduled trigger

In Make“Triggers when a new booking is created.”

Watch New Booking hands your scenario each appointment that has just been booked in Tidycal, one bundle per booking, so the rest of the flow can record it, notify someone or prepare the meeting.

How it fires
scheduled. Make checks Tidycal on the scenario's schedule, so a booking shows up at the next check, not the second it is made.
When to use it
any time a confirmed slot should create work elsewhere, such as a new line in a sales pipeline.
Watch out
a booking that is later canceled still went through this trigger; pair it with Watch Booking Canceled if the difference matters.
Tidycal2Watch Booking Canceled

Watch Booking Canceled

Scheduled trigger

In Make“Triggers when an existing booking is canceled.”

With Watch Booking Canceled, your scenario learns that an existing Tidycal booking was called off and receives it as a bundle, which lets you undo or adjust what the original booking set in motion.

How it fires
scheduled. Make looks for cancellations on the scenario's schedule and processes the ones it finds at that check.
When to use it
when a canceled call should free up a task, change a deal stage or trigger a polite rebooking message.
Watch out
it only covers bookings that already existed; build it as its own scenario next to the one that handles new bookings.
Tidycal3Watch New Contact

Watch New Contact

Scheduled trigger

In Make“Triggers when a new contact is created.”

You get every person newly added to your Tidycal contacts delivered to the scenario, one contact per bundle, ready to land in a CRM, a newsletter tool or a shared sheet.

How it fires
scheduled. Make asks Tidycal for new contacts on the scenario's schedule instead of being told instantly.
When to use it
when the person matters more than the appointment, for example to grow the prospect list in your CRM.
Watch out
it watches contacts, not bookings, so choose Watch New Booking if the meeting itself is what should start the flow.
Modules

What else can Make do with Tidycal?

Tidycal gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Tidycal1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Tidycal API from your scenario, using the same connection as the triggers, which covers the jobs the three listed modules leave out.

When to use it
when you need Tidycal to do something rather than just report it, and no dedicated module exists for that request.
Watch out
you describe the request yourself, so keep the Tidycal API documentation open to find the right endpoint.
Need help

Need help automating Tidycal with Make?

A person reads every message.

FAQ

Tidycal and Make: frequently asked questions

01Is the Tidycal Make integration free?
Yes, Tidycal is a standard app in Make, so it works from the Free plan onward. The Free plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the minimum interval to 1 minute, allow unlimited active scenarios and count usage in credits, meaning operations, per month. An operation is one module running on one bundle.
02What do you need to connect Tidycal to Make?
A Tidycal account and a Make account are enough; the documentation lists no other prerequisite. You add a Tidycal module, click Create a connection, optionally name it, then click Save and confirm access when Tidycal asks. Advanced settings are only for people who bring their own Tidycal app credentials, and in that case the redirect address given in the Make documentation must be entered in the custom app. Once saved, the same connection serves every Tidycal module in all your scenarios.
03Do Tidycal triggers in Make react in real time?
No. All three Tidycal triggers, Watch New Booking, Watch Booking Canceled and Watch New Contact, are scheduled triggers. Make checks Tidycal on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan the shortest gap between two scheduled runs is 15 minutes; paid plans can go down to 1 minute. A booking made just after one check waits for the next one before it is processed. If your case needs a faster reaction, the schedule interval is the first setting to look at.
04What if the Tidycal module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Tidycal API with the connection you already set up, so you are not limited to the three triggers when you need something else from your account. You write the request yourself with the help of the Tidycal API documentation. The Make documentation gives no numeric limit for Tidycal, so there is no published cap to plan around; if something goes wrong, click Run once and read the bundles each module received to see where it stops.
05Should you use Make or n8n for Tidycal?
It depends on where the rest of your workflows already live. In Make, Tidycal comes with 3 scheduled triggers for bookings and contacts plus Make an API Call, and it is available on the Free plan. The same app often has an n8n node as well, so check what each tool actually offers for Tidycal before you commit. Look first at whether the triggers cover your need, and how much you would have to handle through API calls in either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations