Resources · Make integration

freispace Make integrationAutomate freispace with Make.

Can Make react when a project or a booking changes in freispace? Yes: the freispace Make integration brings 51 modules, including 8 triggers. This guide shows how to link your account, then walks you through a first working scenario.

Try the freispace integration on MakeSee the 51 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the freispace Make integration automate?

The freispace Make integration lets Make read and change your freispace data without code: projects, bookings, staff, resources and storages. You build a scenario, the automation made of a chain of modules, where each module is one brick: a trigger that starts things, an action that changes something, or a search.

Storage ready the moment a project exists. Watch New Projects spots a fresh project, then Create a Project Storage gives it its storage entry. Nobody has to open freispace a second time to finish the setup.

A clean record when bookings disappear. Watch Deleted Bookings passes each removed booking to the next module, so you can note it in a sheet or warn the person who relied on it. Pair it with Watch Updated Bookings to follow changes as well.

Staff and resources kept in sync. When someone joins your team in another tool, Create a Staff adds them in freispace, and Update a Staff keeps their record current afterwards. The same pattern works for resources and suites.

What Make does not give you here: the official Make documentation for freispace is short and flagged as AI-generated, so check sensitive details in freispace itself. None of the 8 triggers is instant; they all run on the scenario's schedule. If a gap shows up, Make an API Call covers the rest of the freispace API. Weighing another tool? The n8n vs Make comparison lays out the criteria, and the Make training helps you go further once your first scenario runs. When something breaks, start with Make troubleshooting.

Connect

How do you connect freispace to Make?

  1. 01

    Create an API key in freispace

    In freispace, open your team menu, click Team Settings, go to Integrations and then API keys. Click Create API Key, give it a name, choose its permissions, confirm, and copy the key shown on screen.

  2. 02

    Add a freispace module in Make

    In your Make scenario, add any freispace module and click Create a connection. A connection is your freispace account linked to Make once, then reused by every freispace module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied into the connection window and follow the on-screen instructions to finish. Once saved, Make can list the freispace data the key has access to right inside the module fields.

First scenario

Your first scenario: a storage for every new freispace project

GoalWhen a new project appears in freispace, Make creates a project storage for it.

  1. 01

    Create the scenario

    On the Scenarios page of Make, create a new scenario and click the big + to place the first module on the canvas, where your scenario will take shape.

  2. 02

    Pick the trigger

    Search for freispace, choose Watch New Projects, then click Create a connection and paste your API key. The clock badge on the module means it is a scheduled trigger.

  3. 03

    Add the action

    Click the + on the right of the trigger and pick Create a Project Storage. Fill its fields and map the project data that the trigger hands over.

  4. 04

    Test with Run once

    Create a test project in freispace, then click Run once. Open the bubbles above each module to read the bundles it received, one bundle per project found.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Every module run counts as an operation on your plan.

Triggers

The freispace triggers

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

freispace1Watch Archived Projects

Watch Archived Projects

triggerIn the docs only

Starts your scenario whenever a freispace project gets archived, so the wrap-up work around a finished job happens without anyone having to remember it. Each archived project reaches the next module as one bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and hands over the archived projects it finds.
When to use it
a producer archives a closed job and you want its storage released with Delete a Project Storage.
Watch out
an archived project can come back, so add Watch Reactivated Projects if your cleanup must be undone later.
freispace2Watch Deleted Bookings

Watch Deleted Bookings

triggerIn the docs only

Gives you a trace of every booking removed from freispace, which the app itself no longer shows once it is gone. Your scenario receives each deleted booking and can log it or alert the right person.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along the deletions spotted at that check, not the second they happen.
When to use it
a coordinator cancels a slot and the crew member needs a message in your chat tool.
Watch out
the booking no longer exists in freispace, so a View a Booking placed after this trigger has nothing left to read.
freispace3Watch Deleted Projects

Watch Deleted Projects

triggerIn the docs only

Catches projects that vanish from freispace so the rest of your tools do not keep orphaned folders, rows or tasks. Every deleted project becomes a bundle your next module can use to clean up elsewhere.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes unless you change the clock on the module.
When to use it
a project was created by mistake and its twin in your project tracker must go too.
Watch out
deletion differs from archiving; for projects that are simply closed, Watch Archived Projects is the trigger you want.
freispace4Watch New Bookings

Watch New Bookings

triggerIn the docs only

Turns each new freispace booking into the starting point of your automation: a calendar invite, a message to the person booked, a line in a sheet. The booking arrives as a bundle with its data ready to map.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a booking made just after a check waits for the next one.
When to use it
your team plans people and rooms in freispace and wants the booked crew told without copying anything.
Watch out
on the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute.
freispace5Watch New Projects

Watch New Projects

triggerIn the docs only

Kicks off your scenario each time a project is added in freispace, which makes it the natural first brick for any setup routine around a new job. The project reaches the next module as a single bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule and hands over the projects created since then.
When to use it
every new job needs a project storage, a folder in your file tool or a channel for the team.
Watch out
a project brought back from the archive is not new; Watch Reactivated Projects covers that case separately.
freispace6Watch Reactivated Projects

Watch Reactivated Projects

triggerIn the docs only

Notices when an archived project is brought back to life in freispace, a moment that is easy to miss in other tools. Your scenario gets the reactivated project and can reopen what the archive step had closed.

How it fires
scheduled. Make checks the app on the scenario's schedule, and the clock badge on the module reminds you of it.
When to use it
a client returns with extra work and the old job must reappear in your tracker and your planning sheet.
Watch out
it only makes sense next to an archive flow; if your team never archives, this trigger stays quiet.
freispace7Watch Updated Bookings

Watch Updated Bookings

triggerIn the docs only

Follows changes to existing freispace bookings so the people and tools downstream see the new version rather than an outdated one. Each modified booking is handed to your scenario as a bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a moved slot reaches you at the next check, not the second it changes.
When to use it
a slot moves and the calendar event you created from Watch New Bookings must move with it.
Watch out
if your scenario itself runs Update a Booking, it can trigger this watcher again, so keep the two in separate flows.
freispace8Watch Updated Projects

Watch Updated Projects

triggerIn the docs only

Hands you every freispace project that was edited, so a renamed job or a changed detail spreads to your other tools instead of living in freispace alone. The edited project comes through as one bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, which you set with the clock on the first module.
When to use it
the project name in your accounting or file tool must stay identical to the one in freispace.
Watch out
a scenario that also runs Update a Project can feed this trigger its own changes; filter them or split the flows.
Modules

What the freispace modules can do

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

freispace1

Create a Booking

ActionIn the docs only

Places a new booking in freispace from data that lives somewhere else, so a request filled in a form or an order in another app lands in your planning without retyping.

When to use it
a request form collects a date and a person, and the booking should appear in freispace on its own.
Watch out
check the result with Run once first, since duplicates are easy to create when the trigger fires twice.
freispace2

Create a Project

ActionIn the docs only

Opens a freispace project straight from the tool where the deal or the job starts, which keeps the name and details identical on both sides from day one.

When to use it
a deal is marked as won in your CRM and the production team needs the project waiting in freispace.
Watch out
Watch New Projects will then see this project too, so avoid looping it back into the same scenario.
freispace3

Create a Project Storage

ActionIn the docs only

Attaches a storage entry to a freispace project, the finishing step of a project setup that people usually forget until the files start piling up.

When to use it
right after Watch New Projects, so every fresh project gets its storage without a manual click.
Watch out
map the project from the trigger bundle rather than typing it, otherwise every run targets the same project.
freispace4

Create a Resource

ActionIn the docs only

Adds a resource to freispace from an outside list, handy when your equipment or rooms are tracked in a spreadsheet or an inventory tool first.

When to use it
a new item enters your inventory sheet and should become bookable in freispace too.
Watch out
run List Resources before it when you are not sure the item already exists, to keep one entry per resource.
freispace5

Create a Staff

ActionIn the docs only

Registers a person as staff in freispace using the details your HR or onboarding tool already holds, so the planner can book them as soon as they join.

When to use it
an onboarding form is completed for a new hire or freelancer.
Watch out
the same person entered twice becomes two staff records; search with List Staff first when the source can resend data.
freispace6

Create a Storage

ActionIn the docs only

Declares a new storage in freispace from your scenario, keeping the storage list in the app aligned with what your team actually has on hand.

When to use it
a new drive or storage unit is logged in your asset sheet and freispace should know about it.
Watch out
a storage is not tied to a project here; for a project link, Create a Project Storage is the right module.
freispace7

Create a Suite

ActionIn the docs only

Creates a suite in freispace from Make, which saves you from rebuilding it by hand each time your setup grows.

When to use it
your facilities list in another tool gets a new entry that also needs to exist as a suite in freispace.
Watch out
the Make doc says little about suites, so run it once on a test entry and read the bundle before going live.
freispace8

Delete a Booking

ActionIn the docs only

Removes a booking from freispace when the reason for it disappears in another tool, which frees the slot without anyone opening the planner.

When to use it
a client cancels through your form or CRM and the matching booking must go.
Watch out
a deletion cannot be undone from Make; add a filter before this module so only the intended booking reaches it.
freispace9

Delete a Project

ActionIn the docs only

Wipes a project from freispace as part of a cleanup flow, useful when test projects or duplicates clutter the planner.

When to use it
a deal is lost in your CRM before any work started and the draft project has no reason to stay.
Watch out
there is no going back; if the job may return, archive it in freispace rather than deleting it here.
freispace10

Delete a Project Storage

ActionIn the docs only

Detaches and removes the storage entry of a project, the closing move of a flow that releases storage once a job is done.

When to use it
after Watch Archived Projects, to tidy up the storages tied to finished work.
Watch out
check which project storage you target with View a Project Storage before the delete, because Make will not ask for confirmation.
freispace11

Delete a Resource

ActionIn the docs only

Takes a resource out of freispace when it leaves your inventory, so nobody books equipment or a room that is no longer available.

When to use it
an item is marked as sold or retired in your asset sheet.
Watch out
bookings may still point to that resource; look at them with List Bookings before removing it for good.
freispace12

Delete a Staff

ActionIn the docs only

Removes a staff record from freispace once the person leaves, which keeps the planner showing only people who can really be booked.

When to use it
an offboarding step is completed in your HR tool.
Watch out
the deletion is final, and past bookings tied to that person may matter for reporting, so export what you need first.
freispace13

Delete a Storage

ActionIn the docs only

Drops a storage from the freispace list, the counterpart of Create a Storage when a drive or unit is no longer in use.

When to use it
a storage device is flagged as broken or given back in your asset tracker.
Watch out
project storages may depend on it; run List Project Storages first to see what the removal would affect.
freispace14

Delete a Suite

ActionIn the docs only

Removes a suite from freispace so that your planner stops offering a space or setup that no longer exists.

When to use it
a suite is closed in your facilities list and the change should reach freispace without a manual edit.
Watch out
the doc gives no detail on what happens to linked data, so test on a dummy suite before pointing it at a real one.
freispace15

List Absence Types

SearchIn the docs only

Fetches the absence types defined in your freispace account, a search that returns zero, one or several bundles, one per type.

When to use it
you sync leave requests from an HR tool and need the exact freispace type to match each request against.
Watch out
every bundle it returns runs the following modules once, which counts operations on your plan.
freispace16

List Activities

SearchIn the docs only

Pulls the list of activities stored in freispace, giving your scenario the reference values it needs before creating or updating anything.

When to use it
a report in a spreadsheet should show every activity available in freispace.
Watch out
as a search, it can return no bundle at all; add a filter or a fallback so the next module does not run empty.
freispace17

List Booking Statuses

SearchIn the docs only

Returns the booking statuses your team uses in freispace, so a scenario can translate them into labels your other tools understand.

When to use it
you mirror bookings into a sheet and want a clear status column next to each one.
Watch out
the list rarely changes, so fetching it on every run spends operations for nothing; View a Booking Status suits a single lookup.
freispace18

List Bookings

SearchIn the docs only

Searches freispace for bookings and sends each result down the scenario as its own bundle, the base for summaries and exports.

When to use it
a manager wants the bookings of a project collected in one sheet or one message.
Watch out
many results mean many bundles and many operations after it; group them with an aggregator from Make if you need one message.
freispace19

List Project Storages

SearchIn the docs only

Brings back the storages attached to projects in freispace, which lets a scenario check or report on them before touching anything.

When to use it
before Delete a Storage, to see which projects still rely on it.
Watch out
an empty result is normal for a project without storage, so handle that case instead of treating it as an error.
freispace20

List Projects

SearchIn the docs only

Retrieves the projects in freispace as separate bundles, so you can loop over them to update, export or check each one.

When to use it
you want a sheet listing every project, refreshed whenever your scenario runs.
Watch out
each project it returns pushes the modules behind it into another round, so large accounts use operations quickly.
freispace21

List Resources

SearchIn the docs only

Returns the resources known to freispace, the quick way for a scenario to find out whether an item exists before creating it.

When to use it
ahead of Create a Resource, to avoid adding the same equipment twice.
Watch out
it can return several matches; set a filter after it so only the right resource goes on to the next step.
freispace22

List Sites

SearchIn the docs only

Lists the sites set up in your freispace account, useful when the same flow must behave differently depending on the location involved.

When to use it
a multi-location team needs a sheet or a dashboard showing each site from freispace.
Watch out
like any search, it returns one bundle per site, so the modules behind it run once per location.
freispace23

List Staff

SearchIn the docs only

Pulls the staff records from freispace, the reference your scenario needs to match a person from another tool with the right freispace entry.

When to use it
before Create a Staff, to check whether the new hire is already registered.
Watch out
a name alone can match more than one person; compare a second detail before updating or deleting a record.
freispace24

List Storages

SearchIn the docs only

Returns the storages listed in freispace, one bundle each, so a scenario can compare them with your own asset tracker.

When to use it
you reconcile the storage units in a spreadsheet with the ones declared in freispace.
Watch out
the result covers storages, not their project links; List Project Storages answers that other question.
freispace25

Make an API Call

ActionIn the docs only

Calls any endpoint of the freispace API from your scenario while reusing the connection you already created, which covers what the listed modules leave out.

When to use it
you need a freispace feature that none of the 51 modules exposes.
Watch out
you write the request yourself, so keep the freispace API documentation open and test with Run once before switching the scenario on.
freispace26

Update a Booking

ActionIn the docs only

Changes an existing freispace booking with fresh data from another tool, so a moved date or a new detail reaches the planner automatically.

When to use it
a client reschedules in your booking form and the freispace slot must follow.
Watch out
Watch Updated Bookings will notice this change too; keep both in different scenarios to avoid an endless back and forth.
freispace27

Update a Project

ActionIn the docs only

Edits a freispace project from the outside, keeping its name and details in step with the tool where the job is really managed.

When to use it
the deal name changes in your CRM and freispace should show the same wording.
Watch out
point it at the right project by mapping it from a previous module, never by typing a fixed value.
freispace28

Update a Project Storage

ActionIn the docs only

Adjusts the storage entry of a project in freispace, so what the app records keeps matching the files and drives your team really uses.

When to use it
a project moves to another drive and its freispace storage entry must reflect the change.
Watch out
fetch the current entry with View a Project Storage first if you only want to change part of it.
freispace29

Update a Resource

ActionIn the docs only

Refreshes a resource in freispace with the latest details from your inventory, keeping the planner accurate without manual edits.

When to use it
an item gets renamed or reassigned in your asset sheet.
Watch out
use List Resources beforehand to find the exact resource, especially when two items share a similar name.
freispace30

Update a Staff

ActionIn the docs only

Brings a staff record in freispace up to date whenever the person's details change in your HR or team directory.

When to use it
someone changes role or contact details and the planner should show the new information.
Watch out
match the person on a stable detail rather than the name alone, or the change may land on the wrong record.
freispace31

Update a Storage

ActionIn the docs only

Modifies a storage in freispace from your scenario, so a relabeled unit or a changed detail does not stay out of date in the app.

When to use it
your asset tracker records a change on a storage device.
Watch out
test on one storage with Run once and read the returned bundle before letting the scenario touch the whole list.
freispace32

Update a Suite

ActionIn the docs only

Edits a suite in freispace when its setup changes elsewhere, keeping one description of that space across your tools.

When to use it
your facilities sheet notes a change on a suite that the planner should pick up.
Watch out
the doc says little about suite data, so compare the bundle from Run once with what freispace shows before going live.
freispace33

Upsert Storage Statistics

ActionIn the docs only

Writes storage statistics to freispace, creating them when missing and updating them when they already exist, which spares you the check in between.

When to use it
another tool measures your storage usage and freispace should hold the latest figures.
Watch out
the doc does not describe the statistics expected, so validate the first run in freispace before switching the scenario on.
freispace34

View a Booking

ActionIn the docs only

Reads one freispace booking in full, which gives the next modules every detail in one bundle, ready to map.

When to use it
after Watch Updated Bookings, to fetch the complete booking before writing it into your calendar.
Watch out
it needs a booking that still exists, so it fails after Watch Deleted Bookings.
freispace35

View a Booking Status

ActionIn the docs only

Looks up a single booking status in freispace, turning a status reference into something readable for your message or report.

When to use it
a booking bundle carries a status and your team notification should spell it out.
Watch out
when you need all statuses at once, List Booking Statuses does it in one step instead of repeated lookups.
freispace36

View a Project

ActionIn the docs only

Fetches the full record of one freispace project, so the next module works with every detail rather than only what the trigger passed along.

When to use it
a booking points to a project and your summary email should name that project properly.
Watch out
map the project from the previous bundle; a fixed value would make every run read the same project.
freispace37

View a Project Storage

ActionIn the docs only

Reads one project storage in freispace, the safe look before you change or remove it in the same scenario.

When to use it
ahead of Update a Project Storage or Delete a Project Storage, to confirm the target.
Watch out
if the storage was already removed, the module returns an error, so add a filter or a fallback path around it.
freispace38

View a Resource

ActionIn the docs only

Opens one resource in freispace and hands its details to the rest of the scenario, ideal for enriching a booking with the equipment involved.

When to use it
a booking notification should say which room or item is reserved.
Watch out
each lookup is one operation; for many resources at once, List Resources is lighter on your plan.
freispace39

View a Site

ActionIn the docs only

Retrieves one site from freispace so your messages and reports can mention the location by its proper details.

When to use it
a multi-site team sends booking confirmations that must include where the work happens.
Watch out
the site must come from a previous bundle; typing it in the field freezes every run on one location.
freispace40

View a Staff

ActionIn the docs only

Pulls the record of one person from freispace, which lets a scenario address the right crew member with the right details.

When to use it
after Watch New Bookings, to find the booked person and send them a direct message.
Watch out
if that person was removed with Delete a Staff, the lookup fails, so plan a fallback path.
freispace41

View a Storage

ActionIn the docs only

Reads one storage from your freispace account and hands it to the next module as a single bundle. You get a clean starting point for a report or a message about that storage, without changing it.

When to use it
you already know which storage you care about and want to read it before deciding what the rest of the scenario does.
Watch out
it reads one storage only; when you need to browse them all, start with List Storages instead.
freispace42

View an Absence Type

ActionIn the docs only

Fetches a single absence type from freispace so that later modules can reuse it by name instead of guessing. The result is one bundle, ready to be mapped into an email, a spreadsheet row or a chat message about a team member who is away.

When to use it
a scenario gets an absence type reference and you want the readable version before passing it on.
Watch out
to see which absence types exist in your account, run List Absence Types first and pick one from its results.
freispace43

View an Activity

ActionIn the docs only

Opens one activity defined in freispace and returns it as a bundle, so the modules after it can show what kind of work a booking covers. This keeps a notification or a planning summary readable for people who never log into freispace.

When to use it
a new booking comes in with an activity attached and you want its details before notifying the team.
Watch out
this module only reads; it cannot change the activity, and List Activities is the way to browse every activity at once.
Need help

Need help automating freispace with Make?

A person reads every message.

FAQ

freispace and Make: common questions

01Is the freispace Make integration free?
Yes, on the Make side. freispace is a standard app, available from the Free plan. That plan allows 2 active scenarios, a shortest interval 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits per month. You still need an active freispace account; its own subscription terms are on the freispace pricing page.
02What do you need to connect freispace to Make?
An active freispace account and an API key. In freispace, open the team menu, go to Team Settings, then Integrations and API keys, and create a key with a name, the permissions your scenarios need and an optional expiration date. Copy the key, add any freispace module in Make, click Create a connection and paste it. The connection is then reused by every freispace module in your scenarios, so this setup happens only once per account.
03Are the freispace triggers instant or scheduled in Make?
Scheduled, all 8 of them. Make does not wait for freispace to call it: it checks the app on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. A new booking or project therefore shows up at the next check. Make counts operations on your plan, so a tighter schedule deserves a look at your usage.
04What if a freispace module is missing in Make?
Use Make an API Call. It reaches any endpoint of the freispace API with the connection you already set up, so you are not limited to the 51 listed modules. Keep in mind that the Make documentation for freispace is brief and marked as AI-generated, with a note to verify important details. For anything sensitive, check the freispace API documentation or ask freispace directly, then test the call with Run once before activating the scenario.
05Make or n8n for freispace?
It depends on where the rest of your automations run and on what your team already knows. On Make, freispace offers 51 modules, 8 scheduled triggers and Make an API Call for anything missing, with a visual editor and a Free plan to start. If n8n is already part of your setup, check whether it offers a freispace node and compare the two on the criteria that matter to you: modules available, triggers, and how your team prefers to build.
Same platform

Other docs you might need on this stack.

Browse all integrations