Docs & wikis · native integration

Create a Notion database item from every form response

Each response becomes a page in a Notion database you already work from, with answers filling the properties named like your questions and the full set listed inside the page, so your board views, filters, owners and status properties can take it from there. Use it when responses need triage rather than storage.

Start free — no card All Notion details

Available on Pro, $14.99 a month. The free plan covers Google Sheets, Zoho CRM, Zapier, calendar sync, webhooks, and email notifications.

Four steps, start to finish

This is a native integration, so there is a Connect button in the builder and nothing to install.

Create the database in Notion first

Zunoform writes into a database that already exists. Add a property for each answer you want to filter by, named like the question, plus the triage properties you want, such as Status and Owner. The title property can have any name.

Connect the workspace and grant access

Click Connect on the Notion card. Notion asks which pages or databases Zunoform may write to — the target database has to be one of them, or it will not appear in the next step.

Select the database

Pick it from the list. Each new response is created as a page in it.

Enable and test

Turn it on and submit one response. Check the matching properties are filled and the full answer list is in the page body. An empty property usually means its name doesn't match the question label.

What arrives on the other side

One database item per response. Answers fill the properties whose names match the question labels (hidden fields such as utm_source match by parameter name), converted to the property type: text, number, select, multi-select, date, email, phone, URL or checkbox. The title property, whatever it's called, gets the form name and submission date unless a question shares its name. Every answer and hidden-field value is also written into the page body as a “Question: answer” list, so answers with no matching property, or with a type the API can't write (files, people, relation, status, formula), are still there. Status and owner stay properties your team fills during triage.

When it fires, and what happens if it fails

Every action on this page fires on a completed response, not on a partial one. The response is stored in Zunoform first and delivered from a queue, so a failure on the far side is retried rather than dropped. One thing to plan for: responses collected before you switch the integration on are not replayed. Delivery starts from the moment it is enabled, and anything earlier stays in your dashboard for CSV export.

Questions people ask

Which plan includes Notion?

Pro, at $14.99 a month, alongside Slack, HubSpot, Mailchimp, Airtable, and Excel.

Can Zunoform create the database for me?

No. Create it in Notion, grant access during the connection step, then select it. This is deliberate — writing into a database you built means your own views and triage properties stay in charge.

How is this different from sending responses to Google Sheets?

The artifact, mostly. A sheet is for filtering and pivoting numbers; a Notion database is for moving items through a process with owners and status. Sheets is also on the free plan, while Notion is Pro.