AFI
Airmeet
Airmeet is a virtual events and community platform for webinars, conferences, and meetups. Advanced Form Integration registers attendees for your Airmeet events directly from WordPress form submissions, so every registration, sign-up, or RSVP on your site automatically adds the person to your event’s attendee list.
What you’ll need
- An active Airmeet account.
- An Airmeet Access Key and Secret Key (see below).
- At least one event created in your Airmeet account.
- The Advanced Form Integration plugin installed and activated.
Get your Airmeet API keys
Airmeet uses a two-step authentication flow. AFI exchanges your Access Key and Secret Key for a bearer token via the Airmeet auth endpoint, then uses that token for all API calls. The token is cached for 25 days and refreshed automatically.
- Sign in to airmeet.com and open the Community Manager (CM) dashboard.
- Go to Integrations → API Access Keys.
- Copy the Access Key and Secret Key.
- In WordPress, go to AFI → Settings → Airmeet.
- Click Add New Account, paste both keys, and give the account a name.
- Click Save.
Create the integration
- Go to AFI → Add New.
- Give the integration a name, for example
Event registration to Airmeet. - Under Trigger, pick the form plugin and the specific form you want to listen on.
- Under Action → Platform, select Airmeet.
- In Task, choose Register Attendee.
- Pick the saved account in the Airmeet Credentials dropdown.
- Select an Airmeet Event from the dropdown. AFI loads your events automatically from the API (up to 500 events per call).
- Map your form fields onto the Airmeet fields listed below.
- Optional: open Conditional Logic to limit which submissions are sent.
- Click Save Integration.
Tasks supported
Register Attendee
Registers the form submitter as an attendee for the selected Airmeet event via POST /airmeet/{airmeetId}/attendee. The attendee appears in your Airmeet event dashboard immediately. If the email is already registered for the event, Airmeet updates the existing attendee record.
Required fields
| Field | Field key | Notes |
|---|---|---|
email |
Attendee email address | |
| First Name | firstName |
Trimmed to 35 characters |
| Last Name | lastName |
Trimmed to 35 characters |
Optional fields
| Field | Field key | Notes |
|---|---|---|
| Organisation | organisation |
Company or organization. Trimmed to 70 characters. |
| Designation / Job Title | designation |
Trimmed to 70 characters |
| City | city |
Trimmed to 70 characters |
| Country | country |
Trimmed to 70 characters |
| Attendance Type | attendance_type |
IN-PERSON or VIRTUAL. Required for Hybrid Conference format events. |
| Register Attendee | registerAttendee |
Boolean: true = confirmed registration, false = invitation only. Defaults to false. |
| Send Email Invite | sendEmailInvite |
Boolean: true = send email with calendar invite. Defaults to true. |
Field length limits
Airmeet’s API enforces character limits that AFI handles automatically: first and last name are trimmed to 35 characters, and organisation, designation, city, and country are trimmed to 70 characters. You do not need to validate these lengths in your form.
Conditional logic example
Only register attendees who select a specific ticket type. Add a condition: Ticket Type is VIP Pass. Other form submissions are skipped, letting you use a single form for multiple event tracks.
Troubleshooting
Nothing arrives in Airmeet
Open AFI → Log and find the most recent entry for this integration. AFI stores the request it sent and the raw response it got back, so the Airmeet error message is right there. If there is no log entry at all, the trigger never fired: re-check the form selection and submit a real test entry from the front end rather than the form builder preview.
Authentication failed
AFI exchanges your Access Key and Secret Key for a temporary token via POST /prod/auth. If authentication fails, verify both keys are correct and were copied from Integrations → API Access Keys in the Airmeet CM dashboard. The Access Key and Secret Key are both required; either one alone will not work. The token is cached for 25 days; if it expires or is revoked, AFI re-authenticates automatically on the next request.
“Airmeet ID is required”
You must select an Airmeet Event in the integration. Events are loaded from the API after you connect your credentials. If the dropdown is empty, verify your API keys are correct and that you have at least one event created in Airmeet.
Required field errors
AFI validates that Email, First Name, and Last Name are all present before sending. If any of these are blank in the form submission, the request is not sent and the error is logged.
Attendance type error on hybrid events
If your event uses the Hybrid Conference format, the attendance_type field (IN-PERSON or VIRTUAL) is mandatory. Without it, Airmeet rejects the registration. Map this field from a dropdown or radio button on your form.