Every submission lands
in the database the team works in.

The team already runs its work in Notion. Each submission creates a page in that database, with answers mapped to properties and a page template, so nobody retypes the application.

See the plugins See how it works

Hiring pipeline 2 applicants

Each application, its own page.

Mara Moss Senior Developer

In review

Rowan Reed Support Lead

Page added

Role chosen → Matching database

Illustrative experience

A record per submission
Fields mapped to properties
Updates follow entry edits

The finished experience

Nobody retypes a submission into Notion.

New applications arrive already sorted into the properties the team filters, groups, and drags across a board view. An edited entry updates the page it created, so the database keeps up with the form.

A good fit for
Teams who run hiring, feedback or internal requests out of a database that is not WordPress.

1

Connect the form to the database.

Create the database in Notion first — a feed connects to a database that already exists. In the form, open Settings → Notion, click Add New, authorize the Notion account, then choose Connect Existing Database and pick the one this feed writes to.

GC Notion
2

Map the answers, then write the page.

Map each field to the property the team actually filters on: the candidate’s name to Name, the role to Select, the application date to Date, the uploaded résumé to Files & media, and the stage to Status, which is set from options that already exist in Notion. Then build the Page Content Template from headings, lists, and to-dos, typing { to drop in the merge tags that pull the entry’s answers into the page body.

GC Notion
3

Test the feed, then route by answer.

Insert a test page from the saved feed to confirm the connection before real submissions arrive. Then add a feed per destination with its own conditional logic — one application form can send each role to its own database — and switch on Update & Delete Pages so an edited entry rewrites its page.

GC Notion

Written up, step by step

How to Send Gravity Forms Data to Notion How To · April 2025 Discover how simple it is to send Gravity Forms data to Notion — and explore how the Notion connection helps you do even more with your… Read the tutorial

What you’ll need.

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

GC Notion

Creates a page per entry in a Notion database and maps the answers onto its properties. The database has to exist in Notion first.

Explore GC Notion

Taking it further

Add these optional plugins when your project calls for more.

Optional

GP Populate Anything

Optionally reads choices or values from your connected Notion database into form fields. This lookup does not write Notion edits back to existing entries.

Explore GP Populate Anything

Before you start

GC Notion and the Notion account and database your team already uses. The destination database must exist before connecting the feed.
Enable Update & Delete Pages when entry edits should update generated pages. This can replace manual edits to those pages.
This is a one-way push from entries to Notion. Reading database values into a form requires the optional GP Populate Anything integration.

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 NotionConnect

Optional

GP Populate AnythingPerks

Gravity Connect Basic $59 /year

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

Gravity Perks Basic $59 /year

Only if you add GP Populate Anything.

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.

If someone edits the page in Notion, does the entry change?

No. The sync runs one way: Gravity Forms writes to Notion, and Notion never writes back to the entry. With Update & Delete Pages on, an entry edit also replaces that page’s content and properties, so anything typed into the generated page by hand is lost. Pair GC Notion with GP Populate Anything if you need Notion data to reach a form.

Can it create the Notion database for me?

No — create the database in Notion, then connect the feed to it. You can add properties to that database from the feed with Add New Property, and the new property takes the type of the field or entry property you mapped to it.

Which Notion properties can’t be mapped?

Checkbox, Formula, Rollup, Button, and Notion AI Autofill properties are not mappable, and neither are the read-only ones: Created time, Created by, Last edited time, Last edited by, and ID. Relation is not offered in the feed settings and is handled through a filter instead. Status and Person can only be set from options that already exist in Notion.

We use Airtable, not Notion. Is this the same build?

The outcome is similar, but each destination needs its own setup. GC Airtable maps fields to records in an existing base and table; GC Google Sheets maps fields to rows and needs a unique lookup column for updates. Each has its own update/delete settings. A custom REST destination needs API Alchemist requests for every operation you want, including updates, deletes and any read-back endpoint. The Notion page template and its steps do not transfer unchanged.