Survey answers arrive as records.
The charts stay current.

You run the survey in Gravity Forms; the base the rest of the team opens lives in Airtable. Each submission creates a record in the table you pick, with Likert rows, ranked lists and star ratings written to Airtable field types that can be grouped, filtered and charted in an Interface.

Guest experience survey 128 responses

Every answer in its own field.

MM
Mira Moss Rating 5 · Breakfast first
Added
DD
Dorian Dale Rating 3 · Likert, 4 rows
Updated
Survey submitted → Record in Airtable

Illustrative experience

  • Typed Likert, Rank and Rating fields
  • Records that follow entry edits
  • Optional historical backfill

The finished experience

Nobody copies responses into the base.

Responses land in the table as they come in, so the views and charts your team already opens stay current without an export step. The people reading results never have to ask for a fresh file.

A good fit for
Teams running surveys, applications or intake forms in Gravity Forms who report out of Airtable.

  1. 1

    Run the survey in Gravity Forms.

    Build the questions with the Survey Add-On’s fields: a Likert field for the scale questions, with a row per statement, a Rank field people drag into order, and a Rating field for stars. This is the form respondents fill in; nothing about it changes because Airtable is on the other end.

    Gravity Forms Survey Add-On

  2. 2

    Every response lands in the base as a record.

    An Airtable feed under the form’s settings maps each answer to a real Airtable field type: Likert results to single line text, long text or a select field, with each row of a multi-row Likert free to go to its own field; a ranked list to a numbered list in a text field; and a Survey field set to Rating to Airtable’s Rating field. Save the feed and use Insert Test Record to confirm the connection before the form goes live.

    GC Airtable

  3. 3

    Keep the Interface current, corrections included.

    Turn on Update & Delete Records so an edited entry updates its record, a trashed entry removes it and a restored entry puts it back. Optionally add Feed Forge to process responses collected before the feed existed.

    GC Airtable

What you’ll need.

Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.

Taking it further

Add these optional plugins when your project calls for more.

Before you start

  • GC Airtable and the Airtable account your team already uses.
  • The base and table must already exist in Airtable — the Airtable Connection cannot create either one.
  • The Survey Add-On for the Likert, Rank and Rating fields themselves. Airtable’s Rating field caps how many stars it will store, however many the form offers.

Works alongside

Sold and supported by their makers, not by us.

Get this built.

A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.

Required

  • GC AirtableConnect

Optional

Gravity Connect Basic $59 /year

Covers this on one site. More sites need Advanced or Pro.

See plans for this solution

Every plan renews at the same price, and you can upgrade any time for the difference.

Make it fit
your project.

Can I pull Airtable data back into the form?

Not through the Connection. The Airtable Connection documents a one-way push from Gravity Forms to Airtable, plus updates and deletes for the records it already created; reading a table back into the form is not part of it.

What happens when somebody corrects a response after the fact?

Turn on Update & Delete Records in the feed. With it active, editing the entry updates the record it created, trashing the entry or marking it as spam deletes the record, and restoring the entry adds it back, so a corrected answer changes the chart. Leave the setting off and the record stays as it was first written.

Our Likert question has six rows. Do they all land in one field?

Only if you map them that way. A multi-row Likert field can send the result of each row to its own Airtable field, so each statement can be grouped and charted on its own; map the field to a single text or select field instead and the answers arrive together.

  • Clay, CTO
  • Dan, Content Sorcerer
  • Dani, Product Manager
  • David, Founder & CEO
  • Matt, Senior Support Wizard
  • Roxy, Support Wizard

Not quite your build?

Tell us what you are making and we will work out which pieces it takes — or tell you straight if this is not something we can do.

Ask the wizards