TutorialGravity Forms Zoom Integration: Create Zoom Meetings From Booking Forms

Do you want to create Zoom meetings from a Gravity Forms booking form without copying meeting details by hand?

In this tutorial, you will build a practical Gravity Forms Zoom integration using GravityWP API Connector. When someone submits a booking form on your WordPress site, Gravity Forms will send the meeting details to Zoom and create a new Zoom meeting.

We tested this workflow with a simple booking form. The final setup created a Zoom meeting, saved the Zoom meeting ID, saved the join URL, saved the start URL, and stored the full Zoom API response in the Gravity Forms entry.

The workflow looks like this:

Gravity Forms booking form
→ GravityWP API Connector gets a Zoom access token
→ GravityWP API Connector creates the Zoom meeting
→ Zoom meeting details are saved back to Gravity Forms

This tutorial uses the Zoom API and a Zoom Server-to-Server OAuth app. It does not use Zapier.

Zoom’s Meeting APIs allow developers to work with Zoom Meetings and Webinars programmatically, and the Zoom Meetings API server is https://api.zoom.us/v2. Zoom API requests also need an access token, which can be created with Server-to-Server OAuth.

What does this Gravity Forms Zoom integration do?

This Gravity Forms Zoom integration creates a real booking workflow.

When a user submits a Gravity Forms form, GravityWP API Connector first requests a Zoom access token. Then it uses that access token to create a scheduled Zoom meeting.

After Zoom creates the meeting, Gravity Forms stores the returned meeting details in the entry.

The setup saves:

1. Zoom Meeting ID
2. Zoom Join URL
3. Zoom Start URL
4. Full Zoom Meeting Response

This is useful for discovery calls, onboarding calls, consultation forms, support sessions, internal appointments, and other booking workflows.

This tutorial creates a Zoom meeting. It does not create a Zoom webinar registration, register attendees for a webinar, or build a full webinar registration form. Zoom webinars may need different endpoints, scopes, or Zoom plan access.

What you need to integrate Gravity Forms with Zoom

This tutorial is part of the wider Gravity Forms integrations workflow, where form submissions can send data to other apps through APIs.

Before you start, make sure you have:

• A WordPress site
• Gravity Forms installed
• GravityWP API Connector installed
• A Zoom account
• Access to Zoom App Marketplace
• A Zoom Server-to-Server OAuth app
• Permission to create meetings in Zoom

You will also need these values from your Zoom app:

• Account ID
• Client ID
• Client Secret

Keep these credentials private. Do not add them to screenshots, public documentation, or frontend form fields.

Zoom’s Server-to-Server OAuth flow uses app credentials to request an access token. Then the access token is used to make Zoom API requests.

Step 1: Create a Zoom Server-to-Server OAuth app

First, go to the Zoom App Marketplace.

Then go to:

Develop → Build App

Choose:

Server-to-Server OAuth App

Name the app:

Gravity Forms Zoom Meeting Test

A Server-to-Server OAuth app is a good fit for this tutorial because the WordPress site needs to create Zoom meetings inside your own Zoom account. The person submitting the Gravity Forms booking form does not need to connect their own Zoom account.

After creating the app, open the App Credentials section and copy these values into a private note:

1. Account ID
2. Client ID
3. Client Secret

Do not show the Client Secret in any tutorial screenshot.

Zoom’s documentation explains that Server-to-Server OAuth apps are created in the Zoom App Marketplace and use account credentials for API authentication.

Step 2: Add the Zoom meeting scope and activate the app

Next, go to the Scopes section in your Zoom app.

Add this meeting scope:

Create a meeting for a user
meeting:write:meeting:admin

This scope allows the app to create a Zoom meeting for a user in your Zoom account.

For this tutorial, you do not need Event Subscriptions. Leave webhook features turned off. Gravity Forms will trigger the workflow when the form is submitted, so we do not need Zoom to send webhook events back to WordPress.

After adding the scope, go to Activation and activate the app.

Step 3: Create the Zoom Booking Form in Gravity Forms

Now create the booking form in WordPress.

Go to:

Forms → New Form

Name the form:

Zoom Booking Form

Add these public fields:

For the first test, use simple text fields for Meeting Date and Meeting Time. This makes it easier to send the date and time to Zoom in the expected format.

Use values like this:

Meeting Date: 2026-07-30
Meeting Time: 10:00:00

Together, those values create a Zoom start_time like this:

2026-07-30T10:00:00

Step 4: Add hidden admin fields for Zoom data

Add these fields to the same Gravity Forms form:

These fields should be set to Administrative visibility.

They are not for the person filling out the form. They are used to store the Zoom API results in the Gravity Forms entry.

This is important because the Zoom access token and Zoom start URL are sensitive. The start URL is for the meeting host and should not be shown publicly.

Gravity Forms documentation explains that Administrative visibility hides a field from the public form while keeping it available in the admin area.

Step 5: Create the Zoom OAuth Token API connection

Now create the first API connection in GravityWP API Connector.

This API connection gets the temporary Zoom access token.

Go to the API Connector settings and add a new API connection.

Use these settings:

This may look confusing at first. The app is a Server-to-Server OAuth app, but the token request itself uses Basic Auth with the Client ID and Client Secret.

The token request gets an access token from Zoom. That token is then used in the second API request to create the Zoom meeting.

Zoom says Server-to-Server OAuth tokens are valid for one hour.

Step 6: Create the “Get Zoom Access Token” API Connector feed

Go to:

Zoom Booking Form → Settings → API Connector

Create a new feed.

Use these settings:

In the Query String / Body Parameters section, add:

For the target field mapping, use:

Then enable Store full response and select:

Zoom Token Response

GravityWP API Connector can store the full API response in a text field when the request triggers on form submission. This is useful for testing and troubleshooting.

Step 7: Create the Zoom Meetings API connection

Next, create a second API connection.

This one sends the meeting details to the Zoom API.

Go to the API Connector settings and add another API connection.

Use these settings:

Use No authentication here because the Authorization header will be added inside the feed. That header will use the access token saved by the first feed.

Step 8: Create the “Create Zoom Meeting” API Connector feed

Go back to:

Zoom Booking Form → Settings → API Connector

Create another feed.

Use these settings:

Zoom’s Meeting API uses POST /users/{userId}/meetings to create meetings. The API server is https://api.zoom.us/v2, so using the base URL https://api.zoom.us with the endpoint /v2/users/me/meetings gives the correct request URL.

Step 9: Add the Zoom meeting request headers

In the Headers section of the Create Zoom Meeting feed, add:

Use the merge tag picker to insert the correct merge tag for the Zoom Access Token field.

It may look something like this:

Bearer {Zoom Access Token:8}

Your field ID may be different, so use the merge tag picker instead of copying this example exactly.

Step 10: Add the Zoom meeting body parameters

In the Query String / Body Parameters section, add these values:

Use your actual Gravity Forms merge tags.

For example, your values may look like this:

topic → {Meeting Topic:1}
start_time → {Meeting Date:4}T{Meeting Time:5}
duration → {Duration:6}
agenda → {Meeting Notes:7}

The exact field IDs depend on your form.

Here is what each value does:

In our test, we used:

timezone → Asia/Manila

Change this if your site or meeting host uses a different timezone.

Step 11: Map the Zoom response back to Gravity Forms

In the Target Fields section, map the Zoom response values back into your Gravity Forms entry.

Use:

Then enable Store full response and select:

Zoom Meeting Response

This lets you confirm the full Zoom response after each test.

Step 12: Test the Gravity Forms to Zoom workflow

Now submit a test entry.

Use this sample:

After submitting the form, open the Gravity Forms entry.

You should see values saved in these fields:

• Zoom Access Token
• Zoom Token Response
• Zoom Meeting ID
• Zoom Join URL
• Zoom Start URL
• Zoom Meeting Response

In our test, Zoom returned a meeting ID and Gravity Forms saved the meeting details back into the entry.

Then check Zoom:

Zoom Web App → Meetings → Upcoming

In our test, the meeting appeared in Zoom as:

Discovery Call Test

That confirms the full Gravity Forms to Zoom workflow is working.

Why does this setup use two API Connector feeds?

This setup uses two feeds because Zoom requires an access token before the meeting request can run.

The first feed gets the token:

Get Zoom Access Token

The second feed uses that token:

Create Zoom Meeting

The workflow is:

Form submission
→ Get Zoom access token
→ Use token to create Zoom meeting
→ Save Zoom meeting details

This is why the hidden Zoom Access Token field matters. It stores the token from the first request so the second request can use it in the Authorization header.

What about Zoom webinars and registration forms?

This tutorial creates Zoom meetings, not Zoom webinars.

That matters because Zoom webinar workflows can be different. A Zoom webinar registration form may need different API endpoints, scopes, fields, and Zoom plan access.

For example, a webinar registration workflow may involve:

1. Zoom webinar
2. Webinar registration
3. Webinar ID
4. Registrant details
5. Zoom registration
6. Registration form fields

This tutorial does not register attendees for a Zoom webinar. It creates a scheduled Zoom meeting from a Gravity Forms booking form.

If your goal is webinar registration, test that as a separate workflow.

Troubleshooting Gravity Forms and Zoom API errors

If the integration does not work on the first try, check these common issues.

The Zoom access token is not saved

Check:

• The Client ID is correct
• The Client Secret is correct
• The Account ID is correct
• The Base URL is https://zoom.us
• The endpoint is /oauth/token
• The grant_type value is account_credentials
• The response key is access_token

If any of these values are wrong, Zoom will not return the token.

The Zoom meeting is not created

Check:

• The Zoom Access Token field is filled
• The Authorization header starts with Bearer
• The endpoint is /v2/users/me/meetings
• The request method is POST
• The body format is JSON body
• The Zoom app has the create meeting scope

Also check that your token feed runs before the meeting feed.

The meeting time is wrong

Check:

• Meeting Date format
• Meeting Time format
• Timezone value

In our test, we used:

2026-07-30T10:00:00

with:

Asia/Manila

If your timezone is different, update the timezone value in the feed.

The Zoom Join URL is not saved

Check the response mapping.

Use:

Zoom Join URL → join_url

Also check the full Zoom Meeting Response field to confirm that the join_url key exists in the response.

The Zoom Start URL is not saved

Check the response mapping.

Use:

Zoom Start URL → start_url

The start URL is sensitive. Keep it in an Administrative field and do not display it on the public form.

The workflow works once, then fails later

Zoom access tokens expire. In this setup, the token feed runs again on each form submission, then the meeting feed uses the token saved in the entry.

If the meeting feed runs before the token field is filled, the meeting request may fail. In our test, the two-feed setup worked because the token feed ran first and the meeting feed used the saved token.

When should you use n8n instead?

This API Connector setup is useful for a simple no-code workflow:

• Create a Zoom meeting from a Gravity Forms submission
• Save the Zoom meeting ID
• Save the Zoom join link
• Save the Zoom start URL
• Store the full API response

For more advanced automation, you may want to use n8n with Gravity Forms.

n8n may be a better fit when you need:

1. Conditional routing
2. Different Zoom hosts
3. Follow-up emails
4. Calendar invites
5. CRM updates
6. Slack or Telegram notifications
7. Multi-step automation

You can also use GravityWP’s n8n Connector if the main goal is to send Gravity Forms submissions into an n8n workflow.

Conclusion

You now have a tested Gravity Forms Zoom integration that creates a Zoom meeting from a booking form submission.

The setup uses GravityWP API Connector, a Zoom Server-to-Server OAuth app, and the Zoom Meetings API. API Connector first gets a Zoom access token, then creates the Zoom meeting, then saves the returned meeting details back to Gravity Forms.

This workflow can reduce manual tasks when your team collects meeting requests in WordPress and needs Zoom meetings created automatically.

FAQ

Our Premium add-ons for Gravity Forms

DateTime Field

The GravityWP - DateTime Field add-on adds a dedicated Date/Time field to Gravity Forms so users can enter both a date and a time in a single input.

All Entries

All your new Gravity Forms entries in one central place. Stop navigating between multiple forms to find new entries. Get immediate oversight and full control with a powerful, unified dashboard.

Entry to Database

Integrates Gravity Forms with internal or external databases, offering flexible mapping of form fields to database columns and real-time synchronization between entries and database rows.

Advanced Merge Tags

This Gravity Forms Add-On adds extra Merge Tag modifiers (and a lot of power). From the most common used functions like capitalize and length to changing date formats.

See all add-ons

Read tutorials about

Gravity Forms Zoom Integration: Create Zoom Meetings From Booking Forms

Learn how to connect Gravity Forms to Zoom without Zapier using GravityWP API Connector. This step-by-step tutorial shows how to create Zoom meetings from booking form submissions and save the returned meeting details back to Gravity Forms.

Gravity Forms monday.com Integration: Create New Items From Form Submissions

Learn how to connect Gravity Forms to monday.com without Zapier using GravityWP API Connector. This step-by-step tutorial shows how to create new monday.com items from form submissions and save the returned monday.com item ID back to Gravity Forms.

Gravity Forms Pipedrive Integration: Send Form Contacts to Pipedrive Without Zapier

Learn how to connect Gravity Forms to Pipedrive without Zapier using GravityWP API Connector. This step-by-step tutorial shows how to send form contacts, custom fields, and the returned Pipedrive Person ID directly from WordPress to Pipedrive CRM.

Show Previous Gravity Forms Submissions Using Advanced Merge Tags

This step-by-step tutorial shows how to use GravityWP Advanced Merge Tags to count previous Gravity Forms submissions and calculate total submitted value based on a matching email address.

See all tutorials