Resources · Make integration

EasyWeek Make integrationAutomate EasyWeek with Make.

Every new EasyWeek booking can start work in your other tools. The EasyWeek Make integration gives you 2 scheduled triggers, both about bookings. This page is for teams that take appointments and want each one passed on without copy and paste: connect, build a first scenario, pick the right trigger.

Try the EasyWeek integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the EasyWeek Make integration do for you?

The EasyWeek Make integration lets Make notice new bookings in your EasyWeek account and hand them to any other app you use. You build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as a trigger or an action. Here EasyWeek supplies the trigger, and the rest of the chain belongs to other apps.

A booking log that fills itself. Watch New Bookings picks up each appointment and the next module writes it as a row in the spreadsheet your manager already reads. Nobody retypes a calendar again.

A heads-up for the person on duty. For a clinic or a studio, Watch New User Bookings can feed a message into the team chat, so staff see the booking without opening EasyWeek.

A contact in your CRM. A salon that follows up with clients can send each booking to its CRM and start the usual follow-up from there.

Know the limits before you start. EasyWeek offers only triggers in Make: no action to create or change a booking, no search, and no Make an API Call module. Make's own documentation for the app is also marked as limited, so test with Run once before you rely on a scenario. If a step breaks, the Make troubleshooting guide is a good place to look, and Make pricing explains what each plan allows.

EasyWeek may also have an n8n node. To weigh the two tools on your own criteria, read n8n vs Make.

Connect

How do you connect EasyWeek to Make?

  1. 01

    Add an EasyWeek module

    In your scenario, add Watch New Bookings or Watch New User Bookings, then click Create a connection. A connection is your EasyWeek account linked to Make once, then reused by both modules.

  2. 02

    Give the connection a name

    This step is optional, but a clear name such as your business or location helps later, when several accounts or teammates share the same Make organization and you need to pick the right one.

  3. 03

    Authorize Make and save

    Approve access on the EasyWeek page that opens, or paste the key EasyWeek gives you if Make asks for one. Then click Save, and the module can read your account.

First scenario

Your first scenario with EasyWeek

GoalWhen a new appointment is booked in EasyWeek, Make passes it to another app your team uses.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Add the EasyWeek trigger

    Search for EasyWeek, choose Watch New Bookings and click Create a connection to link your account, as described above.

  3. 03

    Add the next app

    Click the + on the right of the trigger, pick the app that should receive the booking, then map the booking data from the EasyWeek module into its fields.

  4. 04

    Test with Run once

    Click Run once, book a test appointment, then open each module to read the bundles it received. A bundle is one item passed along, here one booking.

  5. 05

    Schedule and switch on

    Set the schedule on the clock of the first module, every 15 minutes by default, then switch the scenario on so it keeps checking for bookings.

Triggers

What starts an EasyWeek scenario?

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

EasyWeek1Watch New Bookings

Watch New Bookings

Scheduled trigger

In Make“Triggers when a new appointment is booked.”

This trigger gives your scenario every appointment that gets booked in EasyWeek, one bundle per booking, so the next module can file it, announce it or store it somewhere else.

How it fires
scheduled, so Make checks EasyWeek on the scenario's schedule, every 15 minutes by default, and at most that often on the Free plan.
When to use it
the default choice when any new appointment in your business should reach another tool.
Watch out
each booking it passes on costs operations in the modules that follow, so filter early if only some bookings matter.
EasyWeek2Watch New User Bookings

Watch New User Bookings

Scheduled trigger

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

With this one, your scenario starts from new user bookings created in EasyWeek, which Make's directory describes separately from new appointments. Each booking arrives as its own bundle for the modules after it.

How it fires
scheduled, meaning Make asks EasyWeek for new items at the pace of the scenario's schedule.
When to use it
when the bookings you care about are the user bookings EasyWeek lists as such.
Watch out
the documentation does not explain how these differ from the bookings in Watch New Bookings, so run both once on a test account and compare the bundles before choosing.
Need help

Need help automating EasyWeek with Make?

A person reads every message.

FAQ

Questions about EasyWeek and Make

01Is the EasyWeek Make integration free?
Yes, EasyWeek is a standard app, so its modules work on the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two 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 remove the cap on active scenarios. Make counts usage in operations, one module handling one bundle, so every booking that goes through adds to the count.
02What is needed to connect EasyWeek to Make?
An EasyWeek account and a Make account. The documentation lists no prerequisite and no official connection steps, so the standard Make flow applies: add an EasyWeek module, click Create a connection, optionally name it, authorize Make on the EasyWeek page or paste the key EasyWeek provides, then save. The same connection serves both triggers. Since the documentation for this app is marked as limited, test with Run once straight after connecting.
03Do EasyWeek triggers in Make fire instantly?
No. Both Watch New Bookings and Watch New User Bookings are scheduled triggers, which means Make checks EasyWeek on the scenario's schedule instead of being called by EasyWeek. A new scenario checks every 15 minutes by default. On a paid plan you can shorten that to 1 minute; on the Free plan 15 minutes is the minimum. A booking made just after a check waits for the next one before your scenario sees it.
04What if the EasyWeek module needed in Make is missing?
It depends on what you need. EasyWeek only offers two triggers in Make, with no action, no search and no Make an API Call module, so Make cannot create, change or look up a booking in EasyWeek. You can still use a booking as the starting point and let the other apps in the scenario do the work. For a need the triggers do not cover, check whether another app in your stack handles it, or ask the team for help designing the setup.
05Should EasyWeek be automated with Make or n8n?
It depends on your criteria rather than on EasyWeek itself. On Make, EasyWeek gives you two scheduled booking triggers, a visual editor and a plan system counted in operations. EasyWeek may also exist as an n8n node, which is worth checking before you decide. Compare the modules each tool offers for this app, the tools the rest of your team already uses, and how each one counts usage. The comparison page linked above goes through these points in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations