Match the event and registration
Map the event identifier, form entry ID and required attendee fields into Airtable. Separate the person from the registration: one person may attend several events or register more than one attendee.
WordPress event registration with Make
An event form needs a clear answer to what happens after submission. Norml scopes a Make workflow that reads an agreed Gravity Forms entry, matches the event and records the registration in Airtable. Duplicate submissions, cancellations and waitlists are defined before the roster is used to run an event.
Build a roster your event team can reconcile
The workflow coordinates registration records. A form submission is not automatically a confirmed seat or successful payment.
- Solution
- Automations
- Tools
- WordPress, Gravity Forms, Airtable, Make
- Trigger
- A valid Gravity Forms registration or supported cancellation request is received for an included WordPress event.
- Outcome
- Create or update the matching Airtable registration, assign the agreed roster state and send unresolved capacity or identity cases to the event owner.
Define roster states
Agree requested, confirmed, waitlisted and cancelled states, including who can change them. Missing information and an unknown event go to review rather than landing in a confirmed roster.
Handle changes without extra registrations
Retain the source entry and Airtable record IDs. Repeated delivery updates the existing registration. Define a verified cancellation route and what a changed attendee, event date or ticket quantity means for the original record.
Decide which system owns capacity
Confirm seats through an authoritative rule
Name the system or person responsible for allocating seats. A form-to-Airtable workflow does not by itself provide an atomic reservation when simultaneous submissions compete for the last place. Strict capacity requires a verified reservation mechanism.
Separate payment and communication
Confirm the Gravity Forms fields and Make connection available in your installation. Payment verification, refunds, attendee confirmations, calendar invitations and waitlist offers require separately agreed actions and wording.
Test the registration lifecycle
Map entries and event rules
Review examples for one attendee, multiple attendees and returning registrants. Agree what identifies a duplicate and which details the event team needs to see.
Build the roster mapping
Connect the supported form route and Airtable base. Check permissions, required fields and the source-to-record lookup, then define how incomplete registrations are assigned for review.
Test repeats, cancellations and capacity
Repeat an entry, correct an attendee and cancel a registration. Test competing requests near capacity against the authoritative seat rule. Give the event owner a reconciliation view for entries that did not reach a final roster state.
Related services.
Event registration questions
Can this guarantee we never oversell an event?
Not through a simple form-to-table sequence alone. Concurrent submissions can pass the same availability check. We first identify a reservation system that can enforce capacity or keep requests pending for an authorized allocation step.
How do you distinguish a duplicate from another attendee?
The form entry ID handles repeated delivery of one submission. A second submission needs a separate business rule using the event, attendee and booking context. An email address alone may represent a family, group or returning attendee.
What happens when someone cancels?
A verified cancellation updates the original registration and records its state. Whether it releases capacity or triggers a waitlist offer depends on the authoritative allocation rules. The basic roster workflow does not issue refunds or send messages.
Can the workflow manage a waitlist?
We can scope a waitlist state and review queue. Automatic promotion requires a reliable seat-release signal, ordering policy and acceptance rules. We do not assume that creating a waitlist record reserves a place.
Share the form, event roster and capacity policy. We will define registration identity, cancellation handling and the decisions that need an event owner.