Resources · Zapier integration

MOFFI Zapier integrationAutomate MOFFI with Zapier.

MOFFI Zapier integration: 10 triggers, 4 actions, 1 search. Every trigger is instant, so a booking, an absence or a new user starts your Zap straight away on any plan. Below: what it costs, how to connect, a first Zap to build and what breaks.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MOFFI Zapier integration does for you

The MOFFI Zapier integration links your flexible-work tool to everything else your company uses. MOFFI helps people stay flexible and mobile in their working week: workspace bookings, home office days, absences. Zapier hears about what happens there, from bookings to invoices, and can write back bookings, absences, home office days and users.

Three results come up most. A team that knows who is in: New Booking starts a Zap the moment someone reserves a workspace, and your team chat gets the news. A spreadsheet of remote days: New Home Office adds a row for each home office declaration, so remote days sit in one sheet. New staff ready on day one: a hire recorded in another tool runs Create User, so the person already exists in MOFFI with their company, name, email and locale. All ten MOFFI triggers are instant, so these Zaps start right away, whatever your plan.

What Zapier does not do here matters as much. Create Booking only books free workspaces: a taken one is out of its reach. Nothing booked before the Zap was switched on is picked up, and there is no action to edit or cancel an existing booking. And every trigger and every action asks for a Company, so pick it in each step before you test.

Comparing tools before you build? See our n8n vs Zapier guide, or our Make vs Zapier guide.

Vocabulary

The Zapier words you need, in one minute

Zapier comes with its own vocabulary. Each word is explained once here, in plain terms, then used as is on the rest of the page.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new booking. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like a booking.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, as all ten MOFFI triggers are.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, such as a MOFFI user, so later steps can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
Cost

What a MOFFI Zap really costs

MOFFI is not a premium app, so it works from the free plan. Zapier bills completed actions, never the trigger.

  • Trigger0 tasks
  • Each action that succeeds1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A booking or an absence that starts your Zap costs nothing by itself. Each action that succeeds counts as one task, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: add a filter, a search such as Find User, or a second action, and you need a paid plan. The interval grid below applies to polling triggers only. All ten MOFFI triggers are instant, so it does not apply to them.

Connect

Connect MOFFI to Zapier in three steps

  1. 01

    Open the connections page

    In your Zapier account, go to Apps, then click + Add connection. Before you start, have an account on MOFFI, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick MOFFI

    In the dialog, type the app name, select MOFFI in the results, then click Add connection. A new tab then opens on the MOFFI side for the sign-in, on the MOFFI account you plan to automate.

  3. 03

    Sign in and grant access

    Sign in to MOFFI in that tab, then let Zapier use the account. The connection is saved once, and every MOFFI step of every Zap you build reuses it. On the first test, run the step once and read what comes back before going further.

First Zap

Your first Zap: a shared log of home office days

GoalAdd a row to your spreadsheet each time someone declares a home office day in MOFFI, only for the declarations that pass the filter you set.

  1. 01

    Build: start on New Home Office

    Create a Zap, pick MOFFI as the trigger app and New Home Office as the event, then choose the Company. The trigger is instant, so the Zap starts as soon as a declaration is made.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real declaration rather than on guesses.

  3. 03

    Add a filter (paid plan)

    Click the plus icon, choose Filter, then fill the three boxes: the field to look at, the rule, the value. The Zap becomes multi-step, so it needs a paid plan.

  4. 04

    Add the spreadsheet row

    Pick your spreadsheet app and its add-a-row action, then map the values of the declaration into your columns. The test output shows which values are there.

  5. 05

    Test, read, then publish

    Run each step once and read what came back before going further. When the row looks right, click Publish to switch the Zap on.

Triggers

The 10 MOFFI triggers

10 events start a Zap when something happens in MOFFI, and 10 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Absence

Instant trigger

In Zapier“Triggers when a new absence is created.”

Starts your Zap whenever an absence is recorded in MOFFI. It is the cue for everything that should know someone will be away: a shared calendar, a planning sheet or an inbox.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an absence declared in MOFFI should show up in the planning tool your team actually reads, without anyone copying it over.
Watch out
the trigger asks for a Company; pick it before you run the test.
2

New Booking

Instant trigger

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

Goes off as soon as a booking is created, whoever made it. Of the five booking triggers, this is the one that tells you in advance who plans to use a workspace.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team chat should hear about each reservation when it is made, not on the day itself.
Watch out
map the fields from a real test result, since only the test shows what a new booking carries.
3

Booking Cancelled

Instant trigger

In Zapier“Triggers when a booking is canceled by a member of your company.”

Fires when a member of your company cancels a booking. It closes the loop opened by New Booking, so a seat counted as taken can be counted as free again elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sheet or a channel that announced a reservation should also hear that it fell through.
Watch out
MOFFI describes this event as a cancellation by a member of your company; check at the test that it covers the cancellations you have in mind.
4

Booking Ended

Instant trigger

In Zapier“Triggers when the booking ends.”

Runs your Zap when a booking comes to its end. Paired with Booking Started, it marks both ends of a reservation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
once a reservation is over, a follow-up should go out or an occupancy record should be closed in another tool.
Watch out
like every MOFFI trigger it asks for a Company, to pick before the test.
5

Booking Started

Instant trigger

In Zapier“Triggers when a booking starts.”

Reacts to the moment a booking begins, rather than to its creation. That makes it the trigger for anything tied to the start of the reservation itself.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a welcome note, an attendance line or a presence status should follow the start of the booking, not the reservation made days before.
Watch out
read at the test what each run carries before mapping it.
6

New Home Office

Instant trigger

In Zapier“Triggers when a new home office declaration is created.”

Fires each time someone declares a home office day in MOFFI. It is the remote-work counterpart of New Booking: instead of a seat at the office, a day spent working from home.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team needs one shared view of who works remotely, in a spreadsheet or a planning tool it already opens.
Watch out
declarations made before you published the Zap are not picked up, so the first view starts empty.
7

New Invoice

Instant trigger

In Zapier“Triggers when a new invoice is created.”

Goes off the moment a new invoice is created in MOFFI. Unlike the booking triggers, it follows the money rather than the desks.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each invoice should be logged in a finance sheet or flagged by email, without exporting anything by hand.
Watch out
map the fields from a real test result and not from memory, since only the test shows what an invoice carries.
8

New Quotation

Instant trigger

In Zapier“Triggers when someone create a new quotation in your company.”

Starts the Zap when someone in your company creates a quotation in MOFFI. It comes before New Invoice in the paper trail, at the stage where a price is proposed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a quotation should reach a chosen inbox, or land in the folder where quotes are tracked.
Watch out
the trigger asks for a Company; check at the test what a quotation carries.
9

New User

Instant trigger

In Zapier“Triggers when a new user is added to the company.”

Kicks in when a user is added to the company in MOFFI. It is the starting point of an onboarding Zap: the account exists, and the other tools can follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a new colleague should also appear in the directory, the team channel or the welcome checklist kept elsewhere.
Watch out
the trigger asks for a Company; pick it before you run the test.
10

User Deleted

Instant trigger

In Zapier“Triggers when a new user is removed from the company.”

Tells Zapier when a user is removed from the company in MOFFI. It is the mirror of New User, built for offboarding rather than arrivals.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a departure recorded in MOFFI should be reflected in the lists and sheets where that person still appears.
Watch out
map what you need from the trigger itself, and check at the test which values a removal carries.
Actions

The 4 MOFFI actions

MOFFI gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Declare Absence

Action

In Zapier“Declare a new absence period for a Moffi user with his email address”

Records an absence period for a MOFFI user, identified by their email address, on a given Date and Period.

When to use it
leave approved in another tool should show in MOFFI, so nobody counts on that person being in.
Watch out
the Date expects the format yyyy-MM-ddTHH:mm:ss.SSSZ; check at the test how the date from the earlier step arrives.
2

Create Booking

Action

In Zapier“Create a new booking on MOFFI. You can only book free workspaces.”

Books a workspace in MOFFI for a user, between a start date and an end date, inside the Company and Workspace you pick.

When to use it
a meeting or a visit planned elsewhere should hold a desk or a room in MOFFI too.
Watch out
only free workspaces can be booked, so map one that is free for those dates.
3

Create User

Action

In Zapier“Create a new user”

Adds a new user to a MOFFI company. It requires the Company, an E-mail, a First name, a Last name and a Locale.

When to use it
a person added in another tool should get a MOFFI account without anyone typing it twice.
Watch out
run Find User first if the person may already exist.
4

Declare Home Office

Action

In Zapier“Declare a new home office day for a Moffi user with his email address”

Declares a home office day for a MOFFI user, found by their Email Address, on the Date and Period you set.

When to use it
remote days planned in a shared calendar or a form should be declared in MOFFI as well.
Watch out
the email must match the one the user has in MOFFI.
Searches

The MOFFI search

1 search step looks for data that already exists in MOFFI, so a later step can use it.

A search step looks up something that already exists in MOFFI and hands it to the next steps. In the action list of the editor, searches sit at the bottom, under their own heading. Three settings decide what happens when the lookup does not go as planned.

1

Find User

SearchFind or create

In Zapier“Find an user on Moffi with his email”

Looks up a MOFFI user from their email address, the one required field, and passes the user on to the next steps.

When to use it
a later step such as Create Booking needs the MOFFI user behind an email that came from another tool.
Watch out
the editor also lists Find or Create User. It is this same search with the create box ticked, not an extra operation.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns the search into a find-or-create: it stops offering the setting above and asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a MOFFI Zap breaks

Zapier ties no help article to MOFFI, so the traps below are the general ones, plus the limits MOFFI states on its own actions.

Most come from how Zapier runs a Zap rather than from MOFFI itself. If one of them is already in your way, see our Zapier troubleshooting guide.

  • No catch-up on the past

    A Zap reacts only to what happens after you switch it on. Bookings, absences or users created earlier never start it, and moving that backlog is a separate job.

  • Only free workspaces

    Create Booking can only book a workspace that is free. Map one that is free for the dates you set, and read the test result before you publish the Zap.

  • A Zap that sets itself off

    As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again, and eats tasks fast.

  • A sudden flood held back

    When a trigger returns a huge batch at once, after a bulk import or a migration, Zapier's flood protection can hold those runs back.
Need help

Need help automating MOFFI with Zapier?

A person reads every message.

FAQ

MOFFI Zapier integration: FAQ

01Is the MOFFI Zapier integration free?
Yes, it works on the free plan, because MOFFI is not a premium app. That plan gives you 100 tasks a month and as many Zaps as you want, but each Zap stops at two steps: one trigger and one action. A new booking that posts a message in your team chat fits. Add Find User to look someone up, a filter, or a second action, and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does a MOFFI Zap use?
The trigger costs nothing, so a booking, an absence or an invoice that starts your Zap is free. Each action that succeeds counts as one task, and one that fails is not counted. A Zap that turns each new booking into a chat message uses one task per booking. Count the actions that run each time, then multiply by the bookings, absences or users you expect. A filter or Find User in front makes the Zap multi-step, which needs a paid plan.
03Is the MOFFI integration real time?
Yes, for all ten triggers. Each one is instant: MOFFI tells Zapier itself when the event happens, so the Zap starts right away, whatever your plan. The polling interval of the free plan does not apply to them, and the editor shows a lightning bolt on a Zap built on any of them. The steps that follow, a search or an action, then run in order inside that same run of the Zap.
04What do you need to connect MOFFI to Zapier?
An account on MOFFI, plus read or write access on anything you do not own yourself and want the Zap to touch. In Zapier, open Apps, click + Add connection, search for MOFFI, then click Add connection. A tab opens where you sign in to MOFFI and grant Zapier access. Since every trigger and action asks for a Company, use an account that can reach the company you plan to automate.
05Why does Create Booking fail on some workspaces?
Because MOFFI only lets this action book free workspaces. If the Workspace you map is already taken between the Start date and the End date, it is out of reach for this step. The action also requires the Company and the User, five required fields in all, so check each one is mapped. The free-workspace rule is stated by MOFFI on the action itself. Test with a workspace you know is free and read what comes back before you publish.
06What if the MOFFI operation you need isn't there?
Check the MOFFI page on Zapier, which shows the list of operations currently on offer: today ten triggers, four actions and one search. If you want to change or cancel a booking from a Zap, there is no action for that in the list, so it stays a manual step in MOFFI. Before giving up, look at Find User: with its create box ticked, it covers the case where a person may or may not exist yet.
07Zapier, Make or n8n for MOFFI?
Judge it on criteria, not on a ranking. Availability first: confirm that MOFFI exists as a ready-made step in the other tool's own catalog, with the triggers you rely on. Then Zap length: on Zapier's free plan a Zap holds one trigger and one action, so a lookup with Find User before Create Booking moves you to a paid plan. Then volume: every successful action is a task. The polling interval does not apply, all ten triggers being instant.
Same platform

Other docs you might need on this stack.

Browse all integrations