Resources · Make integration

WaiverFile Make integrationAutomate WaiverFile with Make.

Signed waivers and event updates can travel to your other tools on their own. The WaiverFile Make integration gives you 15 modules: 4 triggers, 8 actions and 3 searches. This guide covers the connection, a first scenario and when to pick each module.

Try the WaiverFile integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the WaiverFile Make integration automate?

The WaiverFile Make integration links your WaiverFile account to Make so waivers and events move without copy and paste. You build a scenario, which is the automation itself: a chain of modules, where each module is one brick that watches, creates, updates, deletes or searches something in WaiverFile.

Every new signature lands where your staff looks. Start a scenario with Watch New Waiver, then pass each waiver to your spreadsheet, chat or CRM. Each waiver travels as one bundle, meaning one item handed from a module to the next.

Your event list stays in step with your booking tool. When a session is added somewhere else, Create an Event adds it in WaiverFile, and Update an Event or Delete an Event keep it current. Search Events finds the right record first.

Changes get noticed. Watch Waiver Updated and Watch Event Updated react when a record is edited, so a follow-up task or message can go out without anyone checking the dashboard.

The listed modules do not cover every part of WaiverFile. For anything missing, Make an API Call reaches other endpoints of the WaiverFile API with the same connection. If you are still weighing tools, the n8n vs Make comparison lays out the differences, and the Make training walks through building scenarios step by step. When a scenario misbehaves, start with Make troubleshooting.

Connect

How do you connect WaiverFile to Make?

  1. 01

    Copy your API key and site ID

    In your WaiverFile dashboard, open Settings in the left menu, click API, then the API keys tab. No key yet? Click Create a Key. Click Show, copy the key, and copy the site ID shown below it.

  2. 02

    Add a WaiverFile module in Make

    Open your scenario in Make, add any WaiverFile module and click Create a connection. A connection is your WaiverFile account linked to Make once, then reused by every WaiverFile module you add later.

  3. 03

    Paste the credentials and save

    Give the connection a clear label in Connection name if you run more than one WaiverFile site; the field is optional. Paste the API key and the site ID you copied, then confirm. Make can now read and write in that account.

First scenario

Build your first scenario with WaiverFile

GoalWhen a session is booked in another tool, Make creates the matching event in WaiverFile.

  1. 01

    Create the scenario

    From the Scenarios page in Make, create a new scenario and click the big + to place the first module. Everything you build next hangs off that circle.

  2. 02

    Pick the starting app

    Search for the tool where bookings are made, such as your form or calendar app, and choose its trigger. It hands each new booking to the scenario as a bundle.

  3. 03

    Add Create an Event

    Click the + on the right of the first module, search WaiverFile and pick Create an Event. Click Create a connection and paste your API key and site ID.

  4. 04

    Map the booking data

    Fill the event fields by clicking the values from the previous module, like the booking name or date. Make shows what it can read from your WaiverFile account once the connection exists.

  5. 05

    Test with Run once

    Click Run once, then create a test booking. Read the bundles each module received, and check that the event appears in WaiverFile.

  6. 06

    Schedule and switch on

    Open Scheduling on the first module. A new scenario runs every 15 minutes by default. Keep it or adjust it, then switch the scenario on.

Triggers

Which WaiverFile triggers can start a scenario?

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

WaiverFile1Watch Event Updated

Watch Event Updated

triggerIn the docs only

Catches events that someone edited in WaiverFile and passes each changed event to the rest of your scenario. It keeps downstream copies, like a shared calendar or a staff sheet, from drifting away from what WaiverFile says.

How it fires
scheduled. Make checks WaiverFile on the scenario's schedule, every 15 minutes by default, so a change shows up at the next check rather than the moment it happens.
When to use it
when a renamed or rescheduled event must be reflected in another tool without anyone retyping it.
Watch out
pair it with Watch New Event if brand-new events matter too, since this one follows edits.
WaiverFile2Watch New Event

Watch New Event

triggerIn the docs only

Starts your scenario each time a fresh event appears in your WaiverFile account. Each new event becomes one bundle that later modules can post, log or copy wherever your team plans its week.

How it fires
scheduled. Make polls WaiverFile at the interval set on the scenario, 15 minutes at the shortest on the Free plan and down to 1 minute on paid plans.
When to use it
when a new event should trigger an announcement in your team chat or a row in your planning sheet.
Watch out
if a scenario also creates events with Create an Event, those will be picked up here as well, so avoid feeding them back into the same flow.
WaiverFile3Watch New Waiver

Watch New Waiver

triggerIn the docs only

Hands you every newly submitted waiver so it can reach the people who need it, without anyone refreshing the WaiverFile dashboard. This is the natural first module for most WaiverFile scenarios.

How it fires
scheduled. On each run of the scenario, Make asks WaiverFile what arrived since the last check and returns the new waivers one bundle at a time.
When to use it
when front desk staff, a coach or an insurer needs to see each signed waiver in their own tool.
Watch out
every waiver processed downstream consumes operations, one per module per bundle, which counts against your Make plan on busy days.
WaiverFile4Watch Waiver Updated

Watch Waiver Updated

triggerIn the docs only

Reports waivers that were changed after submission, so the copy stored elsewhere does not keep outdated details. Think of it as the follow-up watcher to Watch New Waiver.

How it fires
scheduled. Make looks at WaiverFile when the scenario's clock comes around; nothing is pushed to Make the instant a waiver changes.
When to use it
when a spreadsheet or CRM holds waiver details and has to be corrected whenever the waiver is edited in WaiverFile.
Watch out
add a search or update step in the target tool so you edit the existing record instead of creating a duplicate.
Modules

What else can Make do in WaiverFile?

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

WaiverFile1

Create an Event

ActionIn the docs only

Adds a new event to your WaiverFile account from data that lives somewhere else, so nobody has to set it up twice. The booking, form or calendar entry becomes the source.

When to use it
when sessions are planned in another tool and participants must sign against them in WaiverFile.
Watch out
run Search Events first if the same booking can arrive twice, or you will end up with duplicates.
WaiverFile2

Create an Event Category

ActionIn the docs only

Opens a new category in WaiverFile to group events, straight from your scenario. Handy when your catalog of activities grows in another system and WaiverFile should follow.

When to use it
when a new type of activity is added to your offer and its events need a home before they are created.
Watch out
check with Search Event Categories that the name is not already taken.
WaiverFile3

Delete an Event

ActionIn the docs only

Removes an event from WaiverFile when it no longer exists on your side, keeping the list your participants see clean. It acts on one event per bundle.

When to use it
when a session is cancelled in your booking tool and should disappear from WaiverFile too.
Watch out
treat a deletion as final, so test on a dummy event with Run once before switching the scenario on.
WaiverFile4

Delete an Event Category

ActionIn the docs only

Clears out a category you stopped using, so staff are not choosing from stale options when they organize events in WaiverFile.

When to use it
when an activity is retired from your offer and its category should go with it.
Watch out
treat the removal as final; look it up with Search Event Categories and confirm it is the right one before this step runs.
WaiverFile5

Get a Waiver

ActionIn the docs only

Pulls one specific waiver from WaiverFile so later modules can use its content. You point it at a waiver you already identified, often from a trigger or a search.

When to use it
when a scenario knows which waiver it needs and has to read the full record before sending it on.
Watch out
it reads a single waiver; to find several, use Search Waivers instead.
WaiverFile6

Make an API Call

ActionIn the docs only

Reaches any endpoint of the WaiverFile API from inside your scenario, reusing the connection you already created. It is the fallback when none of the named modules does what you need.

When to use it
when a WaiverFile feature has no dedicated module in Make and you know which API endpoint handles it.
Watch out
you write the request yourself, so keep the WaiverFile API documentation open while you set it up.
WaiverFile7

Search Event Categories

SearchIn the docs only

Looks through your WaiverFile categories and returns the matches, zero, one or several, each as its own bundle. It answers the question of whether a category already exists.

When to use it
before creating, updating or deleting a category, to work on the right one.
Watch out
when nothing matches, the next modules receive no bundle and simply do not run, which is easy to mistake for an error.
WaiverFile8

Search Events

SearchIn the docs only

Finds events in WaiverFile and returns each result as a separate bundle for the following modules. Use it to locate the record a later step should touch.

When to use it
when a booking change arrives from another tool and you need the matching WaiverFile event before updating or deleting it.
Watch out
several results mean the next modules run several times, one operation each; narrow the search when you expect a single event.
WaiverFile9

Search Waivers

SearchIn the docs only

Retrieves the waivers that match what you are looking for, so you can check whether a person has already signed or gather a set for a report.

When to use it
when another app asks about a participant and the answer depends on a waiver on file in WaiverFile.
Watch out
each waiver returned is one bundle, and every module after the search runs once per bundle.
WaiverFile10

Update an Event

ActionIn the docs only

Edits an existing WaiverFile event so it reflects changes made elsewhere. The event keeps its identity; only the values you map are rewritten.

When to use it
when a session moves or gets renamed in your booking tool and WaiverFile has to match.
Watch out
updating events can wake a scenario built on Watch Event Updated, so make sure the two do not send changes back and forth.
WaiverFile11

Update an Event Category

ActionIn the docs only

Changes a category you already have in WaiverFile, for example to follow a rename in your activity catalog, without deleting and rebuilding it.

When to use it
when a category label changes in the system that owns your offer and WaiverFile should show the new wording.
Watch out
identify the category with Search Event Categories first, so the edit lands on the one you meant.
Need help

Need help automating WaiverFile with Make?

A person reads every message.

FAQ

WaiverFile and Make: common questions

01Is the WaiverFile Make integration free?
Yes, on the Make side. WaiverFile is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs at most every 15 minutes, stops each execution after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) remove the scenario limit and go down to a 1 minute interval. You still need your own WaiverFile subscription, since Make does not provide the account.
02What do you need to connect WaiverFile to Make?
You need an active WaiverFile account and an API key. In WaiverFile, go to Settings, then API, then the API keys tab, create a key if none exists, reveal it with Show and copy it along with the site ID listed below. In Make, click Create a connection on any WaiverFile module and paste both values. The connection is then reused by every WaiverFile module. Keep the key private, since anyone holding it can act on your WaiverFile data.
03Do WaiverFile triggers in Make work in real time?
No. The four WaiverFile triggers are scheduled: Make checks WaiverFile on the scenario's schedule instead of being notified the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is the shortest interval, while paid plans allow 1 minute. For most waiver and event workflows that delay is fine, but plan for it. Watch the clock badge on the first module to confirm how often it runs.
04What if a WaiverFile module is missing in Make?
It depends on the endpoint. The integration has 15 modules focused on waivers, events and event categories. For anything they do not cover, the Make an API Call module can call any endpoint of the WaiverFile API with the connection you already set up. You write the request yourself, so check the WaiverFile API documentation first. The Make documentation for this app also warns that its text may contain mistakes, so verify key details with WaiverFile.
05Should you use Make or n8n for WaiverFile?
It depends on what your team already uses. On Make, WaiverFile comes with 15 ready modules, a visual editor and a Free plan to start testing. The same app often has an n8n node as well. The honest criteria are the modules each tool offers for WaiverFile, the platform your other automations already run on, and who will maintain the scenarios. Try the Make version with Run once before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations