You want to capture form responses directly into a Notion database without manual data entry. Notion does not have a built-in form builder, but it supports third-party integrations and workarounds that send form submissions into a database table. This article explains how to connect a form tool like Jotform, Typeform, or Google Forms to a Notion database using built-in integrations or automation platforms. You will learn two reliable methods to embed form submissions and keep your database updated automatically.
Key Takeaways: Embedding Form Submissions Into Notion
- Jotform + Notion Integration: Directly maps form fields to database columns without a third-party automation tool.
- Google Forms + Zapier: Sends each form response as a new row in a Notion database using a trigger-action workflow.
- Make (Integromat) for Complex Mappings: Handles conditional logic and multiple database updates from a single form submission.
How Form-to-Database Connections Work in Notion
Notion does not include a native form creator. Instead, it provides an API that external services use to create, update, or delete database items. When a user submits a form, the form tool or automation platform sends a request to the Notion API. The request includes field values that map to specific columns in your database.
To make this work, you need three things:
- A Notion database with columns that match the form fields you want to capture.
- A form builder or automation service that supports the Notion API.
- A connection key called an integration token, which grants the external service permission to write to your database.
The most common services for this task are Jotform, Typeform, Google Forms with Zapier, and Make. Each method uses the same Notion API endpoint but differs in setup complexity and field-mapping flexibility.
Method 1: Embed a Jotform Form Into a Notion Database
Jotform offers a direct Notion integration that does not require a separate automation tool. You create a form in Jotform, map each question to a Notion database column, and submissions appear as new rows instantly.
- Create a Notion database with the columns you need
Open your Notion workspace and create a new database. Add columns such as Name, Email, Message, and Date. The column types must match the data you expect. Use a Text column for names and an Email column for email addresses. - Generate a Notion integration token
Go to Settings & Members > Integrations > Develop or manage integrations. Click New integration. Give it a name, select the workspace, and choose the capabilities needed. Copy the Internal Integration Secret token. This token is the password that Jotform uses to write data. - Connect the integration to your database
Open the database in Notion. Click the three-dot menu in the top-right corner and select Add connections. Choose the integration you just created. The database now accepts API writes from that integration. - Create a Jotform form
Log in to Jotform and create a new form. Add fields that correspond to your Notion columns. For example, add a Name field and an Email field. - Set up the Notion integration in Jotform
In the form builder, go to Settings > Integrations. Search for and select Notion. Paste the integration token. Map each form field to the corresponding Notion database column. Save the settings. - Test the form submission
Open the form in a browser tab, fill it out, and submit. Return to your Notion database. A new row with the submitted data should appear within seconds.
Method 2: Use Google Forms With Zapier to Write to Notion
Google Forms does not have a direct Notion integration. Zapier acts as the bridge. When a Google Form is submitted, Zapier sends the data to a Notion database using the Notion API.
- Prepare your Notion database
Create a database with columns that match your form fields. Use the same column name format as in Method 1. Add the Notion integration to the database using the same steps described above. - Create a Zapier account and start a new Zap
Log in to Zapier. Click Create Zap. Choose Google Forms as the trigger app and select New Form Response as the trigger event. - Connect your Google Form
Select the Google account that owns the form. Choose the specific form from the list. Zapier will fetch a sample submission to understand the field structure. - Set Notion as the action app
Add a new step and select Notion as the action app. Choose Create Database Item as the action event. Connect your Notion account by providing the integration token. - Map form fields to database columns
In the action configuration, select the target database. For each column, click the field and choose the corresponding Google Forms question from the dropdown. For example, map the Name question to the Name column. - Turn on the Zap
Test the Zap with a sample submission. If the test creates a row in Notion correctly, turn on the Zap. All future form responses will flow into your Notion database.
Common Integration Problems and How to Fix Them
Form Submission Does Not Create a Row in Notion
The most common cause is an incorrect or missing integration token. Check that the token was copied exactly and that the database has the integration connected. In Zapier, run the action step test again and look for error messages. A 401 error means the token is invalid. A 404 error means the database ID is wrong.
Data Appears in the Wrong Columns
Field mapping mismatches cause this. In Jotform, verify that each form field is mapped to the correct column name. In Zapier, check that the Google Form question names match the Notion column names. Rename columns or form fields to be identical to avoid confusion.
Duplicate Rows Appear After Each Submission
This usually happens when Zapier or Make is set to process multiple triggers. Check the Zap settings to ensure it runs only on new form submissions. In Make, verify that the webhook is not being called multiple times. Disable any test mode or replay features.
Notion Integration Token Expires or Stops Working
Internal integration tokens do not expire unless manually revoked. If the token stops working, go to Settings & Members > Integrations, click the integration name, and regenerate the token. Update the token in your form tool or Zapier connection immediately.
Jotform vs Google Forms + Zapier vs Make: Integration Comparison
| Feature | Jotform | Google Forms + Zapier | Make (Integromat) |
|---|---|---|---|
| Direct Notion integration | Yes, built-in | No, requires Zapier | No, requires Make |
| Free tier limit | 100 submissions per month on free plan | 100 tasks per month on Zapier free plan | 1000 operations per month on Make free plan |
| Conditional logic in form | Yes, built-in | Yes, via Google Forms sections | Yes, via Make routers |
| Field mapping interface | Drag-and-drop column match | Dropdown selection per field | Custom JSON mapping |
| File upload to database | Not directly supported | Not directly supported | Not directly supported |
| Setup time | 10 minutes | 20 minutes | 30 minutes |
Jotform is the fastest option for simple forms. Google Forms with Zapier works well if you already use Google Workspace. Make is best when you need advanced logic, such as creating multiple database items from one submission or updating existing rows.
All three methods require the same initial step: creating a Notion integration token and connecting it to your target database. Without that token, no external service can write to your database.
You now have two working methods to embed form submissions into a Notion database. Start with Jotform for a quick setup or use Google Forms with Zapier if you prefer a free form builder. For advanced use cases, explore Make to add conditional routing. After setting up the integration, test with a single submission and verify the database row appears before scaling up to live forms.