Resources · Zapier integration

EasyWeek Zapier integrationAutomate EasyWeek with Zapier.

The EasyWeek Zapier integration gives you 2 triggers, 0 actions and 0 searches. It reads new bookings from your salon calendar and hands them to another app. It never writes back into EasyWeek, so plan your workflow around that.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the EasyWeek Zapier integration actually does

EasyWeek is an online appointment tool built for the beauty trade. Plugging it into Zapier means one thing: every time a booking appears in EasyWeek, an automation picks it up and passes it to another app you already use. The integration only listens. It does not create, edit or cancel anything inside EasyWeek.

Three results people usually want from it. First, a running booking log: New Bookings feeds each fresh appointment into a spreadsheet, so the owner sees the week fill up without opening the booking screen. Second, a team ping: the same trigger posts a short message in a chat channel, so the stylist on duty knows a slot just got taken. Third, a client file that stays current: New User Bookings pushes each booking created for a user into a CRM or a mailing list, ready for a follow-up message.

Now the limits, because they shape everything. There is no action on EasyWeek's side, so no Zap can block a slot, move an appointment or update a client record there. There is no search step either. And both triggers are polling ones: Zapier checks EasyWeek on a timer rather than being told the moment a client books (the gap depends on your plan, as the cost section shows).

If writing back into EasyWeek matters, compare with the EasyWeek Make integration before you build. For a wider view of the tool itself, read our Zapier review.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event that starts the Zap. Here, a booking that shows up in EasyWeek. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes a row, sends a message or files a record in another app.
Task
What Zapier bills you for: one action that completes successfully. Your plan's monthly allowance is a count of these.
Polling trigger
A trigger Zapier checks on a timer. It asks EasyWeek for recent items, keeps the new ones, ignores the rest.
Instant trigger
A trigger the app reports itself, the moment the event happens. EasyWeek offers none of these on Zapier.
Filter
A step that lets the Zap carry on only when the incoming booking matches a condition you set, and stops it otherwise.
Connection
Your EasyWeek account linked to Zapier once, then reused by every step in every Zap that touches EasyWeek.
Cost

What it really costs

Good news first. EasyWeek is not a premium app, so it works on the free plan. The bill is counted in tasks, and the trigger itself never costs one.

  • Trigger cost0 tasks, whatever the polling frequency
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo, available on the free plan
  • Filter or second actionMakes the Zap multi-step, paid plan required

Checking EasyWeek for new bookings is free, however often Zapier looks. Only a completed action is counted, and an action that fails is not. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. The moment you add a filter or a second action, the Zap becomes a multi-step Zap and needs a paid plan. Every successful action then counts on its own, so a Zap with three actions uses three times the tasks of a single-action one.

Connect

Connect EasyWeek to Zapier in 3 steps

  1. 01

    Open your Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an EasyWeek account first, with access to the bookings you want the Zap to read.

  2. 02

    Find EasyWeek and start the link

    Type EasyWeek in the search box of the dialog, select it, then click Add connection. A new tab opens on EasyWeek's side, where the rest of the link happens.

  3. 03

    Sign in and grant access

    Log in to EasyWeek in that tab and allow Zapier to reach the account. The connection then appears on your Apps page, and every future Zap reuses it without asking again.

First Zap

Your first Zap: log color appointments in a sheet

GoalA nail and hair salon wants only its coloring appointments copied into a Google Sheets tab, to plan dye orders.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose EasyWeek as the app and New Bookings as the event. Then select the EasyWeek connection you made earlier.

  2. 02

    Test the trigger on a real booking

    Run the test. Zapier brings back the three latest bookings. Pick one and look at what it contains: that is where you spot the value that tells a coloring slot apart.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field, a text rule and the value you noted. A text rule on a text value, or the filter never lets anything through.

  4. 04

    Add the Google Sheets action

    Add Google Sheets with Create Spreadsheet Row, pick the file and tab, and map the booking details into the columns. Each row written counts as one task.

  5. 05

    Test, then publish

    Test the action and check the row in the sheet. Then click Publish. With the filter, this is a multi-step Zap, so it needs a paid plan.

Triggers

EasyWeek triggers on Zapier

2 events start a Zap when something happens in EasyWeek. Zapier checks for them at the interval your plan allows.

1

New Bookings

Polling trigger

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

Starts your Zap each time an appointment gets booked in EasyWeek. It is the broad one: every new slot taken on the calendar comes through, and its details are ready to map into the next step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a shared booking log, or a chat alert for whoever runs the front desk that day.
Watch out
appointments booked before the Zap went live never come through, so moving that backlog is a separate job.
2

New User Bookings

Polling trigger

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

Fires when a booking is created for a user in EasyWeek. Choose it when the Zap is about the person behind the appointment rather than the calendar slot itself.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
feeding a CRM or a newsletter list so each client gets a follow-up after the visit.
Watch out
run the test on both triggers and compare what each returns before you pick one, since the official description stays short on the difference.
When it breaks

When an EasyWeek Zap breaks

Zapier attaches no help article to EasyWeek, and no rate limit specific to the app is documented. What breaks is the general behavior of Zapier.

Four cases cover most surprises on a booking Zap. None of them shows up as an error message, which is exactly why they catch people out.

  • Old bookings never arrive

    A Zap only reacts to what happens after you switch it on. Appointments already on the calendar stay where they are; moving them is a separate job.

  • A booking batch is held back

    After a bulk import into EasyWeek, the trigger may suddenly return a huge batch. Zapier's flood protection can hold that batch back instead of running it all.

  • The filter never passes

    Filter rules are typed. A number rule on a text value, or the reverse, blocks every booking. Match the rule to what the test showed.

  • The same booking shows up once only

    Zapier remembers what it already saw on a polling trigger. The same booking never starts the Zap twice: that is by design, not a bug.
Need help

Need help automating EasyWeek with Zapier?

A person reads every message.

FAQ

EasyWeek Zapier integration: frequent questions

01Is the EasyWeek Zapier integration free?
Yes, EasyWeek is not a premium app, so it runs on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one EasyWeek trigger and one action in another app. Add a filter or a second action and you need a paid plan. No price is quoted here because Zapier changes its grid often; the pricing page on zapier.com is the reference.
02How many tasks does an EasyWeek Zap use?
One task per successful action, nothing for the trigger. Zapier checking EasyWeek for new bookings costs nothing, however often it looks. So a Zap that writes one spreadsheet row per booking uses one task per booking. A Zap that writes a row and also posts a chat message uses two tasks per booking. An action that fails is not counted against your plan, which keeps a broken step from draining the allowance.
03Does EasyWeek send bookings to Zapier in real time?
No, both EasyWeek triggers are polling triggers. Zapier checks for new bookings at a fixed interval set by your plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. On paid plans you can also run a check by hand from the editor. EasyWeek has no instant trigger on Zapier, and that type is set by the app, not something you can switch on.
04What do you need to connect EasyWeek to Zapier?
An EasyWeek account, plus access to the bookings the Zap should read. From the Apps page of Zapier, click + Add connection, search EasyWeek, click Add connection, sign in on the EasyWeek tab and grant access. The connection is then reused by every Zap you build later. Book one test appointment before testing, since the trigger test pulls the three most recent items and comes back empty on a new account.
05Why are existing EasyWeek appointments missing from the Zap?
Because a Zap only picks up what happens after it is switched on. Every appointment already on the calendar when you published stays out of reach of the trigger. If you need that history in your sheet or CRM, moving it there is a separate job, done outside this Zap. From then on, Zapier tracks what it has seen, so each new booking starts the Zap one time only, never twice.
06What if the EasyWeek operation you need does not exist on Zapier?
Then this integration cannot do it, and that is likely if the job is to write into EasyWeek. Zapier lists 2 triggers for EasyWeek and no action or search at all, so creating, moving or cancelling an appointment from another app is simply off the table here, with no workaround. The realistic options are to keep EasyWeek as the starting point only, or to check whether another automation platform covers the missing step.
07Zapier, Make or n8n for EasyWeek?
It depends on the direction of your workflow. On Zapier, EasyWeek only works as a starting point: two polling triggers, no action, no search, and it runs on the free plan for a two-step Zap. If reading new bookings is enough and the team already uses Zapier, that covers it. If you need anything written into EasyWeek, Zapier cannot do it, so check the other platforms' EasyWeek pages before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations