Resources · Make integration

Gravity Forms Make integrationAutomate Gravity Forms with Make.

What happens to a form entry after someone clicks Submit? The Gravity Forms Make integration gives you 12 modules: 1 trigger, 7 actions and 4 searches. This page shows how to link your site, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Gravity Forms Make integration do?

The Gravity Forms Make integration links the forms on your WordPress site to Make, a tool where you build a scenario (an automation made of bricks called modules) without code. Make picks up new entries, reads forms and their results, and can remove entries, forms or feeds you no longer need.

Route every new lead. Watch Entries spots each entry submitted in a form, and the next module sends it wherever your team works: a CRM, a spreadsheet, a chat channel. The Airtable Make integration is a common landing spot for that data.

Keep an eye on form performance. Get Form Results returns the entry counts of a form, and List Forms gives you every form on the site. Put them together and a marketer can see which form collects the most entries without opening WordPress.

Clean up what piles up. Remove an Entry, Remove a Form and Remove a Feed delete items or send them to the trash, which helps a site admin retire test forms and spam entries once they are identified.

What the module list does not include: there is no module to create or update an entry or a form, and the only trigger is scheduled, so Make checks for entries on the scenario's clock instead of being called by your site. Make an API Call covers the endpoints the listed modules skip. n8n often has a node for the same app; our n8n vs Make comparison helps you choose, and the Make training takes you further once your first scenario runs.

Connect

How do you connect Gravity Forms to Make?

  1. 01

    Get your keys in WordPress

    Make talks to Gravity Forms with a pair of credentials, the Consumer Key and the Consumer Secret. You generate them in the WordPress admin of the site that hosts your forms, then keep both values at hand.

  2. 02

    Open a Gravity Forms module

    In a Make scenario, add any Gravity Forms module, for example Watch Entries. The module asks for a connection, which is your Gravity Forms account linked to Make once and reused by every module of the app. Click Create a connection.

  3. 03

    Paste the credentials and confirm

    Paste the Consumer Key and the Consumer Secret in the window Make opens, then confirm. Once the connection works, the module lists the forms Make can read, which tells you the keys are right.

First scenario

Your first scenario with Gravity Forms

GoalWhen someone submits a new entry in Gravity Forms, Make fetches the updated entry counts of that form.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor. Search for Gravity Forms and pick Watch Entries.

  2. 02

    Connect and set the trigger

    Click Create a connection and paste your two keys. Then fill the module fields: Make lists the forms it can read, so you choose the one to watch from a menu.

  3. 03

    Add Get Form Results

    Click the + on the right of Watch Entries, pick Get Form Results and point it at the same form. Each new entry, called a bundle in Make, now leads to a fresh count.

  4. 04

    Test with Run once

    Submit a test entry on your site, then click Run once. Open the bubble above each module to read the bundles it received and check that the count moved.

  5. 05

    Schedule and switch on

    Click the clock on Watch Entries to set how often Make checks the form. A new scenario runs every 15 minutes by default. Switch the scenario on and it keeps working without you.

Triggers

What starts a Gravity Forms scenario

1 module starts a scenario when something happens in Gravity Forms. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Gravity Forms as soon as it happens.

Gravity Forms1Watch Entries

Watch Entries

Scheduled trigger

In MakeTriggers when a new entry is submitted in a form.

Every entry that lands in the form you pick becomes the starting point of your scenario, with its answers ready to pass to the next module. It is the entry point for almost any Gravity Forms automation.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and 15 minutes at the shortest on the Free plan (1 minute on paid plans).
When to use it
a quote request or signup form whose answers must reach your CRM or your sales team without anyone copying them.
Watch out
entries wait for the next check before Make sees them; test with Run once after a real submission to see what the trigger hands on.
Modules

What the Gravity Forms modules do

Gravity Forms gives you 11 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

7 modules

Note: The Feed ID can be retrieved using the List Feeds module.

Note: The Feed ID can be retrieved using the List Feeds module.

Gravity Forms1

Remove a Feed

Action

In MakeDeletes a specific feed.

This module deletes one feed from Gravity Forms, which clears out a link between a form and an add-on that no longer serves any purpose on your site.

When to use it
retiring an old feed after a form changed hands or a campaign ended, as part of a cleanup scenario.
Watch out
the module needs the feed ID, which you get from List Feeds; place that search before this action.
Gravity Forms2

Get Form Results

Action

In MakeAggregates results (entry counts) of a form.

Here you get the entry counts of one form in a single step, a quick answer to how well that form is doing without exporting anything.

When to use it
after each new entry, or before sending a report, when a marketer wants the running total of a contest or survey form.
Watch out
it returns counts, not the entries themselves; use List Entries of a Form to read the answers.
Gravity Forms3

Get an Entry

Action

In MakeGets an entry based on the entry ID.

Give it an entry ID and it hands back that single entry with all its answers, ready to map into the next module of the scenario.

When to use it
another app stored the entry ID earlier, for example in a support ticket, and you now need the full submission again.
Watch out
it reads one entry by its ID only; to find entries without knowing the ID, go through one of the list searches.
Gravity Forms4

Get a Form

Action

In MakeGets the details of a form based on the specified form ID.

With a form ID, this module returns the details of that form, so later modules know which form they are dealing with and can label the data correctly.

When to use it
a scenario watches several forms and you want each message sent to your team to carry the form's details, not just a number.
Watch out
it describes the form, not its entries or its counts; pair it with Get Form Results when you need both.
Gravity Forms5

Remove an Entry

Action

In MakePermanently deletes a specified entry or moves it to the trash

Once an entry has been handled elsewhere, this action takes it out of Gravity Forms, either sending it to the trash or deleting it for good.

When to use it
a spam entry was flagged by an earlier module, or a lead was copied to your CRM and should not stay on the WordPress site.
Watch out
a permanent delete cannot be undone; test with Run once on a dummy entry and prefer the trash while you tune the scenario.
Gravity Forms6

Remove a Form

Action

In MakePermanently deletes a form or moves it to the trash.

This action removes a whole form from your site, to the trash or permanently, which keeps the forms list short when campaigns come and go.

When to use it
an agency closing a client event, where the registration form and its test copies should disappear after the event.
Watch out
a permanent delete cannot be reversed; read what you need with List Entries of a Form first, and keep the trash option until you trust the flow.
Gravity Forms7

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

When no listed module does what you need, this one lets you call any endpoint of the Gravity Forms API with the connection you already set up.

When to use it
you need something the ready-made modules skip, such as creating or updating an entry; check first that the Gravity Forms API documentation offers it.
Watch out
you write the request yourself, so keep the Gravity Forms API documentation open and test each call with Run once before switching the scenario on.

Searches

4 modules
Gravity Forms8

List Entries of a Form

Search

In MakeGets entries associated with a specific form.

This search returns the entries of one specific form, each as its own bundle, so the next module processes them one by one.

When to use it
you just connected Make and want to send the entries a form already holds to a spreadsheet before Watch Entries takes over for the new ones.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which multiplies operations.
Gravity Forms9

List Entries

Search

In MakeLists all entries for this account.

Rather than one form, this search pulls entries from the whole account, which helps when your data is spread over many forms.

When to use it
building a single archive of every submission on the site, whatever form it came from, in a database or a sheet.
Watch out
every entry it returns is a bundle that the next modules process; when you care about a single form, List Entries of a Form keeps the run lighter.
Gravity Forms10

List Feeds

Search

In MakeReturns all the feeds.

List Feeds brings back all the feeds configured in Gravity Forms, with the IDs the other feed module expects.

When to use it
just before Remove a Feed, to find the feed to delete, or to review which add-ons are wired to your forms.
Watch out
each feed comes out as a separate bundle; add a filter between modules so that only the feed you target reaches the delete step.
Gravity Forms11

List Forms

Search

In MakeGets the details of all forms.

You get the details of every form on the site, one bundle per form, which is the starting point for any scenario that loops over all of them.

When to use it
feeding Get Form Results for each form, so a site owner sees in one table which forms bring entries and which sit idle.
Watch out
modules placed after it run once per form, so a site with many forms uses more operations per run.
Need help

Need help automating Gravity Forms with Make?

A person reads every message.

FAQ

Gravity Forms and Make: common questions

01Is the Gravity Forms Make integration free?
Yes on the Make side: Gravity Forms is a standard app, available from the Free plan. That plan allows 2 active scenarios, a check every 15 minutes at the shortest, 5 minutes of run time and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. On the Gravity Forms side, the Make documentation says the modules need a paid Gravity Forms account, so the license is the cost to plan for.
02What do you need to connect Gravity Forms to Make?
Three things: a paid Gravity Forms account, access to the WordPress admin of the site, and a Make account. In WordPress you generate a Consumer Key and a Consumer Secret. In Make you add a Gravity Forms module, click Create a connection and paste both values. The connection is then shared by the 12 modules of the app, so you do this once per site, not once per scenario. Keep the two keys private, like a password.
03Does the Gravity Forms trigger fire instantly?
No. Watch Entries is a scheduled trigger: Make checks your site for new entries on the scenario's schedule, which is every 15 minutes by default. You can shorten the interval to 1 minute on a paid plan; the Free plan keeps 15 minutes as the minimum. For a contact form that feeds a sales team, that delay is usually fine. To see it in action, submit a test entry, click Run once and open the bubble above Watch Entries: the new entry shows up as a bundle, ready for the next module to use.
04What if a Gravity Forms module is missing in Make?
Use Make an API Call. It sends any request to the Gravity Forms API with the same connection, which is the way to reach what the 12 ready-made modules leave out, such as creating or updating entries, provided the Gravity Forms API documentation lists it. You write the request yourself, so the Gravity Forms API documentation becomes your reference. The Make documentation gives no numeric limit for this app, so the module list and the API are the real boundaries. Test every custom call with Run once first.
05Should you use Make or n8n with Gravity Forms?
It depends on the tool your team already runs. Make offers 12 ready-made Gravity Forms modules, a visual editor and a guided connection, which suits people building their first automations. n8n often has a node for the same app, so check its catalog for Gravity Forms before deciding. Compare the actions each one covers for your case rather than the brand, and pick the tool your team will actually maintain.