Resources · Make integration

RegFox Make integrationAutomate RegFox with Make.

What if every new RegFox subscription reached your team without anyone copying it by hand? The RegFox Make integration gives you 30 modules: 2 instant triggers, 17 actions and 11 searches. This guide is for event and membership organizers, and it walks you from the connection to a first working scenario.

Try the RegFox integration on Make See the 30 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RegFox Make integration do for you?

The RegFox Make integration links your RegFox account to Make, a no-code automation tool. You build a scenario (the automation itself, a chain of bricks called modules) that reacts when a form goes live or a subscription arrives, then reads or updates registrants, coupons and orders for you.

Check-ins that follow your guest list. Check In by ID and Check Out by ID let another tool, like a badge scanner app or a spreadsheet, record when a registrant arrives and leaves in RegFox. Nobody retypes names at the door.

Coupons you manage from one place. Create a Coupon, Update a Coupon and Delete a Coupon cover the whole life of a discount code, so a sponsor deal or a partner offer can be set up from the tool where it was agreed.

Subscriptions your team hears about right away. Watch New Subscriptions is an instant trigger: RegFox calls Make the moment a subscription is added, and the next module can post it wherever your team works.

The listed modules read and update records but do not cover every corner of the RegFox API; Make an API Call fills that gap with the same connection. The same app often has an n8n node too, and the n8n vs Make comparison lays out the criteria. New to the tool? The Make training starts from scratch, and the Make pricing page explains how operations are counted.

Connect

How do you connect RegFox to Make?

01
Generate an API key in RegFox
Log in to RegFox, open the account dashboard, then the Settings section and the API option. Click the button that generates a new API key and copy it. You need an active RegFox account for this step.
02
Add a RegFox module and create the connection
In your Make scenario, add any RegFox module and click Create a connection. A connection is your RegFox account linked to Make once, then reused by every RegFox module. Give it a clear name in Connection name if you run several accounts.
03
Paste the key and save
Paste the API key you copied, or follow the instructions shown on screen, and save. Make now lists what it can read from your account, so you pick forms and records from menus instead of typing identifiers.

First scenario

Your first scenario with RegFox

GoalWhen a form is published in RegFox, Make pulls the inventory list of that form so you can check stock before registrations open.

01
Create the scenario
Open the Scenarios page in Make, create a new scenario and click the big + to add the first module. Search for RegFox and pick Watch Forms Published.
02
Set up the webhook and connection
Click Create a webhook, then Create a connection and paste your RegFox API key. RegFox now warns Make each time a form goes live.
03
Add List Inventories
Click the + to the right of the trigger and add List Inventories. This search asks for a form ID: map it from the data the trigger received, if its bundle carries one.
04
Test with Run once
Click Run once, then publish a test form in RegFox. Open each module's bubble to read the bundles it received and confirm the form ID was passed along.
05
Switch it on
When the test looks right, save and switch the scenario on. An instant trigger does not wait for the default 15-minute schedule: it runs as soon as RegFox calls Make.

Triggers

What starts a RegFox scenario

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

RegFox1Watch Forms Published

Watch Forms Published

Instant trigger

In Make“Triggers when a form is published.”

Watch Forms Published starts your scenario the moment a RegFox form goes live, so the setup work around a new event can begin without anyone keeping an eye on the dashboard.

How it fires

instant, RegFox calls Make through a webhook as soon as the form is published. There is no polling interval to wait for.

When to use it

you want a colleague notified, a coupon prepared or the inventory checked each time a registration page opens.

Watch out

click Create a webhook before Create a connection, or the trigger never receives anything.

RegFox2Watch New Subscriptions

Watch New Subscriptions

Instant trigger

In Make“Triggers when a new subscription is added.”

Watch New Subscriptions hands your scenario each subscription added in RegFox, which makes it the natural starting point for member welcome flows and recurring payment follow-up.

How it fires

instant, RegFox calls Make through a webhook the moment a new subscription exists.

When to use it

a membership program where the finance or community team wants every new subscriber logged in their own tool without exporting lists.

Watch out

each subscription is one bundle, and every module after it uses operations, so keep the chain short while you test.

Modules

Everything else RegFox can do in Make

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

RegFox1

Check In by Display ID

Action

In Make“Check in registrant by display ID.”

Marks a registrant as arrived using the display ID, the reference people tend to see and carry, so a scan or a typed code at the entrance updates RegFox directly.

When to use it

your door team works from the reference shown to attendees rather than from the internal record ID.

Watch out

map the display ID, not the internal ID: this module expects the reference attendees see.

RegFox2

Check In by ID

Action

In Make“Check in registrant by ID.”

Records an arrival in RegFox from the registrant's ID, which suits flows where an earlier module already returned the full registrant record.

When to use it

after Search Registrants or Get a Registrant, when the ID is sitting in the previous bundle and you only need to flip the status.

Watch out

run it once per person; a search that returns several registrants will check in each of them.

RegFox3

Check Out by Display ID

Action

In Make“Check out registrant by display ID.”

Signs a registrant out using their display ID, which gives you a clean record of who left a session or a venue without editing entries by hand.

When to use it

multi-session events or workshops where exit scans matter as much as entry scans and the badge carries the display reference.

Watch out

check the value you map is the display ID and not the internal one.

RegFox4

Check Out by ID

Action

In Make“Check out registrant by ID.”

Closes a registrant's attendance from their ID, the counterpart of Check In by ID for scenarios that already hold the full record from another module.

When to use it

a form or kiosk in another app sends an exit event and you look the person up first, then pass the ID here.

Watch out

map the ID from the lookup, never a display reference, and test the chain with Run once first.

RegFox5

Create a Coupon

Action

In Make“Creates a new coupon.”

Adds a new discount code to RegFox from inside your scenario, so an offer agreed in a CRM, a sheet or a chat thread exists in RegFox without a manual copy.

When to use it

a partner or sponsor is approved in another tool and should receive their own code right away.

Watch out

each run creates one more coupon, so make sure the trigger fires only once per partner.

RegFox6

Delete a Coupon

Action

In Make“Deletes an existing coupon.”

Removes a coupon from RegFox for good, the cleanest way to shut down a code that leaked or an offer that has ended.

When to use it

a deal is cancelled in your CRM and the matching code must stop working in RegFox too.

Watch out

a deleted coupon cannot be brought back from Make; if you might reuse it, Update a Coupon is the safer move.

RegFox7

Get a Coupon

Action

In Make“Retrieves an existing coupon.”

Fetches one coupon and all its details so the next module can report on it or decide what to do with it.

When to use it

you already know which coupon you mean, for example from an earlier bundle, and want its current state before changing or sharing it.

Watch out

it needs the coupon's identifier; to find a code without it, start with List Coupons instead.

RegFox8

Get a Customer

Action

In Make“Retrieves an existing customer.”

Pulls the full record of one RegFox customer, handy when a bundle only gives you a reference and you need the rest of the profile.

When to use it

an order or subscription arrives and you want the buyer's details before creating a contact in your CRM.

Watch out

one run returns one customer; to go through many, List Customers is the right module.

RegFox9

Get a Form

Action

In Make“Retrieves an existing form.”

Returns the details of one RegFox form, which lets a scenario describe an event or registration page accurately in a message or a report.

When to use it

right after Watch Forms Published, when the trigger gives you the form reference and your team needs the rest of the information.

Watch out

check with Run once what the trigger bundle holds before mapping the identifier.

RegFox10

Get a Membership

Action

In Make“Retrieves an existing membership.”

Reads a single membership from RegFox so your scenario can see what a member signed up for before taking the next step.

When to use it

a membership association wants to enrich a welcome email or a member directory entry with the membership's own details.

Watch out

it targets one known membership; to scan them all, List Memberships returns several bundles.

RegFox11

Get an Order

Action

In Make“Retrieves an existing order.”

Retrieves one order from RegFox, the piece you need when accounting or support has to see exactly what was bought.

When to use it

a support ticket mentions an order and you want the scenario to attach the order details to the reply.

Watch out

an order is not a transaction; for payment movements, Get a Transaction is the module you want.

RegFox12

Get a Registrant

Action

In Make“Retrieves an existing registrant.”

Brings back one registrant's record, so a scenario can greet, badge or follow up with the right person using RegFox as the source.

When to use it

you hold a registrant ID from another module and need the full entry before a check-in or a message.

Watch out

it targets one person; to find someone by criteria or pull several, use Search Registrants.

RegFox13

Get a Subscription

Action

In Make“Retrieves an existing subscription.”

Fetches one subscription with its details, useful to confirm the state of a recurring plan before your scenario acts on it.

When to use it

a member writes in about their plan and the scenario should look it up before routing the request.

Watch out

for a subscription that just arrived, the trigger bundle may already hold what you need, so check with Run once to avoid an extra operation.

RegFox14

Get a Ticket

Action

In Make“Retrieves an existing ticket.”

Retrieves one ticket from RegFox, so a scenario knows exactly which admission it deals with before sending anything to the attendee.

When to use it

you print or email badges from another tool and need the ticket details that go on them.

Watch out

it reads one ticket only; List Tickets is the choice for a full export.

RegFox15

Get a Transaction

Action

In Make“Retrieves an existing transaction.”

Returns a single payment transaction, the detail finance teams ask for when they reconcile RegFox with their bookkeeping.

When to use it

a transaction reference lands in another system and you want the matching RegFox record next to it.

Watch out

a transaction and an order are separate records, so pick the module that matches the question your team asks.

RegFox16

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends any request the RegFox API allows, using the same connection, which covers what the other modules leave out.

When to use it

a need no module handles, when someone on your team can read the RegFox API documentation.

Watch out

Make does not guide the fields here the way it does in other modules, so test every call with Run once before switching the scenario on.

RegFox17

Update a Coupon

Action

In Make“Updates an existing coupon.”

Changes an existing coupon in RegFox, so you can extend or tweak an offer without deleting it and starting over.

When to use it

a partner deal is renegotiated in your CRM and the code in RegFox should follow the new terms.

Watch out

map only the values you mean to change, and run it once on a test coupon before touching live codes.

RegFox18

List Coupons

In Make“Retrieves a list of coupons.”

Returns your coupons as a series of bundles, one per code, ready to be filtered or sent to a sheet.

When to use it

you want an overview of active discount codes for a sponsor report or a quick audit.

Watch out

every coupon returned becomes a bundle, and each later module spends operations on each one; List Global Coupons covers the account-wide list.

RegFox19

List Customers

In Make“Retrieves a list of customers.”

Brings back customers in bulk, so a scenario can sync the people who bought from you into a CRM or a mailing tool.

When to use it

a first import into a new tool, before an instant trigger takes over for new arrivals.

Watch out

a long list means many bundles and many operations downstream, so add a filter right after it.

RegFox20

List Forms

In Make“Retrieves a list of forms.”

Lists your RegFox forms, which gives a scenario an index of every registration page you run.

When to use it

you build an event calendar or an internal catalog and want each form to appear there.

Watch out

to react to new forms as they appear, Watch Forms Published is lighter than listing everything again and again.

RegFox21

List Global Coupons

In Make“Retrieves a global list of coupons.”

Pulls the coupon list at the account level, broader than List Coupons, for a view of every code across your RegFox setup.

When to use it

finance or marketing wants a single sheet with all discounts in use, whatever the form.

Watch out

run it next to List Coupons with Run once and compare the two outputs before you rely on either for a report.

RegFox22

List Inventories

In Make“Retrieves a list of inventories by form ID.”

Returns the inventory entries of one form, so your team sees what is left before registrations run out.

When to use it

just after a form is published, or before sending a promotion, to check there is still room.

Watch out

it works form by form and asks for the form ID; pair it with List Forms to cover several events.

RegFox23

List Memberships

In Make“Retrieves a list of memberships.”

Lists memberships in RegFox, a quick way to feed a member directory or a renewal follow-up sheet.

When to use it

you set up a member portal in another tool and need every current membership loaded once.

Watch out

each membership turns into a bundle, so keep the modules after it lean to save operations.

RegFox24

List Orders

In Make“Retrieves a list of orders.”

Returns RegFox orders in bulk, which helps accounting pull every purchase into a spreadsheet or an invoicing tool.

When to use it

after an event closes, to reconcile sales with the numbers your bookkeeping holds.

Watch out

for a single known order, Get an Order spends one operation instead of many.

RegFox25

List Subscriptions

In Make“Retrieves a list of subscriptions.”

Lists subscriptions from RegFox so you can review recurring plans in the tool your team actually opens.

When to use it

a one-off catch-up import before Watch New Subscriptions handles the new ones as they come.

Watch out

running the list and the trigger on the same data will push duplicates into your destination.

RegFox26

List Tickets

In Make“Retrieves a list of tickets.”

Returns tickets as individual bundles, handy to build an attendee sheet or a badge print run from another app.

When to use it

ahead of an event, when the venue or the printer needs the whole ticket list.

Watch out

a large event means a long list, so filter by what you need before sending each ticket onward.

RegFox27

List Transactions

In Make“Retrieves a list of transactions.”

Brings back RegFox transactions in bulk so finance can match payments against bank lines without exporting files.

When to use it

an end-of-event reconciliation where every payment needs a line in your accounting sheet.

Watch out

one transaction becomes one bundle; watch your operation count on large exports.

RegFox28

Search Registrants

In Make“Searches registrants or lists them all.”

Finds registrants matching your criteria, or returns them all, which makes it the usual first step before a check-in or a message.

When to use it

a door app sends a name or an email and you need the matching registrant before checking them in.

Watch out

it can return zero, one or several people, so decide what the next module does with each case.

Need help

Need help automating RegFox with Make?

A person reads every message.

FAQ

RegFox and Make: common questions

01Is the RegFox Make integration free?

Yes, RegFox is a standard app in Make, so you can use it from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of run time at most and files up to 5 MB. Paid plans lower the interval to 1 minute and allow unlimited active scenarios. Make counts usage in operations, one per module run on one bundle, so a scenario that lists many records spends more than one that handles a single subscription.

02What do you need to connect RegFox to Make?

You need an active RegFox account and an API key. Generate the key in RegFox from the account dashboard, under Settings, then the API option, and copy it. In Make, add a RegFox module, click Create a connection, optionally name it, and paste the key. For the two instant triggers, click Create a webhook before Create a connection. The connection is then shared by every RegFox module in your scenarios.

03Do RegFox triggers in Make react in real time?

Yes, both RegFox triggers are instant. Watch Forms Published and Watch New Subscriptions receive a webhook from RegFox as soon as the event happens, so they do not wait for the 15-minute default schedule a polling trigger would use. You still need to switch the scenario on for Make to accept those calls. The other modules have no clock of their own: they run whenever the scenario reaches them, one after the other.

04What if a RegFox module you need is missing in Make?

It depends on the gap, but Make an API Call usually covers it. That module sends any request the RegFox API accepts, using the connection you already set up, so you are not limited to the 17 actions and 11 searches listed. It asks for more care than a guided module, so test it with Run once. The RegFox documentation in Make also warns its content is generated and may contain mistakes, so check important details with RegFox.

05Should you use Make or n8n for RegFox?

It depends on the tool your team already works in. Make offers RegFox as a native app with 30 modules, including 2 instant triggers, and a visual editor where you test each step with Run once. The same app often has an n8n node as well. Compare the modules each side offers for the RegFox tasks you actually need, like check-ins or coupons, and pick the platform where those are covered without extra API work.

Generate an API key in RegFox

Add a RegFox module and create the connection

Paste the key and save

Create the scenario

Set up the webhook and connection

Add List Inventories

Test with Run once

Switch it on

Need help automating RegFox with Make?