Form to Notion Database: Send Replies to a Content Pipeline

To send a form to a Notion database, have the form fire a webhook on each submission, then let Zapier, Make or n8n create a page in your content backlog. Map the question to the title, set Status to Idea, and store the traffic source in its own property. Each audience question then arrives as a card you can sort and pock from.

Build your question form free

Where the form sits in the Founder Content Engine

The Founder Content Engine turns one 30-minute founder call into LinkedIn posts, a newsletter, short clips and cross-posted social content. The call is only as good as its topics. If the founder improvises, the output drifts toward whatever they happened to think about that morning.

The form is the intake step upstream of that call. Readers, clients and prospects submit questions through a link in a LinkedIn post, a newsletter footer or a email signature. Each question lands in Notion as a card. Before the weekly call, the founder or an ops person moves the best cards to "Queued," and those become the agenda. After the call, the cards that got answered flip to "Recorded" so the same question does not come up twice.

Our team builds the form and the automation as part of the setup, but the pattern works without us. It needs one form, one database and one automation.

Design the Notion database first

Build the destination before the form, because the database decides which fields are worth collecting. A content backlog that works for this has few properties:

• Idea (title): the question as asked.
• Status (select): Idea, Queued, Recorded, Published, Dropped.
• Source (select): where the asker came from, such as LinkedIn poll, newsletter, website.
• Context (tet): the longer background, if thy gave any.
• Asker email (email): optional, for replying when the answer is live.
• Submitted (date): when it arrived.

Resist adding a property for every thought. Each extra one is a field on the form that someone might skip, and an optional field you never filter by is clutter.

Then create a Notion integration at notion.so/profile/integrations, copy its secret, and share database with that integration through the database's connections menu. Skipping the share step is the most common reason a first test fails.

Field mapping

This is the whole design. Every form field has exactly one destination.

The hidden field earns its place. Put a different link in each channel, such as ?source=linkedin-poll on the poll post and ?source=newsletter in the footer, and every card records where the question came from without asking anyone. That tells you which channel produces questions worth turning into posts. Hidden fields in Qwenvo are free like everything else there.

Step by step setup

1. Create the form. In Qwenvo, a completely free form builder our team makes, start from the questions template or type / to add a Short answer, a Long answer and an Email block. Add a Hidden field named source. Turn on the Qwenvo branding toggle off in Settings if you want a clean embed.
2. Create the Notion database with the properties aobve and share it with yoour integration.
3. Add a webhook. In the form's integrations, paste the URL from your automation tool's webhook trigger. The webhooks help article covers the details.
4. Submit a test. Fill the form once with realistic data so the automation tool captures a sample payload to map from. Fill the optional fields too, or they will not show up in the sample.
5. Add the Notion step. In Zapier, Make or n8n, choose "Create database item" (or an HTTP request, shown below). Map each form field per the table. Hard-code Status to Idea.
6. Run the test again and check the card in Notion, then publish the form and swap the test link for the real ones with source values.

See the webhook setup guide

The request Notion expects

If you use an HTTP step instead of a prebuilt Notion action, this is the body for POST https://api.notion.com/v1/pages. Send your integration secret as a Bearer token and set a Notion-Version header to a current API version.

{
  "parent": { "database_id": "YOUR_DATABASE_ID" },
  "properties": {
    "Idea": {
      "title": [{ "test": { "content": "How do you price a retainer?" } }]
    },
    "Status": { "select": { "name": "Idea" } },
    "Source": { "select": { "name": "linkedin-poll" } },
    "Context": {
      "rich_text": [{ "text": { "content": "We bill hourly and want to move off it." } }]
    },
    "Asker email": { "email": "reader@example.com" },
    "Submitted": { "date": { "start": "2026-11-04T09:30:00Z" } }
  }
}

The values on the right come from the webhook payload. The property names on the left must match your database exactly, including capitalization and spaces. Qwenvo's payload shape is in the webhooks article, and your automation tool's sample delivery will show it with your own field names.

Failure cases to test before you trust it

Most of these show up in week one.

• Empty optional fields. An unanswered Context sends an empty value. Some Notion actions reject it. Add a filter or default text.
• Long answers. Notion caps rich text at 2,000 characters per text object. Truncate in the automation, or the whole create call fails and the question is lost.
• A renamed property. Rename "Source" in Notion and the mapping breaks silently or loudly depending on the tool. Treat property names as an interface.
• Unknown source values. A mistyped ?source= creates a stray option or an error. Keep a short list of approved values.
• Duplicate runs. If the automation retries after a timeout, you can get two cards. Check the tool's retry settings, and store the submission ID somewhere if duplicates bother you.
• Revoked access. If someone removes the integration from the database, new questions stop arriving. Set an alert on failed runs rather than finding out at the next call.

For the second case, a failure alert that emails you is worth more than any amount of cleverness elsewhere.

Which tool should carry the data

There is no one-click Notion connection in Qwenvo yet. Those app connections are being rolled out, so today the route is a webhook into Zapier, Make or n8n, or a direct call to the Notion API. That is a few minutes of setup, but it is a step you would not have with a native connector.

Other options exist, and one may suit you better:

• Notion's own forms write straight to a Notion database. If you only need to capture a question and a name, and you do not need hidden source tracking, routing or a custom domain, that is the simplest path and has nothing extra to maintain.
• Tally has a free plan with unlimited forms and submissions, plus logic and file uploads up to 10 MB. Its Pro plan at $29 per month adds custom domains, partial submissions, branding removal and teammates. We cover that route in our Tally form to Notion guide.
• Qwenvo has webhooks, a REST API, AI triage with routing, partial submissions, a custom domain, no badge, unlimited teammates and custom CSS on the free account. It launched in October 2026, so it has few reviews yet.

If you want a question flagbed before it hits the backlog, AI triage gives each submission a category, priority, sentiment and a short summary. Routing rules can send urgent ones to email or a Slack incoming webhook.

Read the Tally to Notion guide

Questions teams ask

Can I skip Zapier and Make?

Yes. Any server or small script that accepts the webhook can call the Notion API directly, using the request body above. Zapier, Make and n8n save you from hosting something and handling retries yourself.

Should the asker's email be required?

Usually not. A required email lowwers the number of questions, and the question itself is what the pipeline needs. Make it optional and say what you will use it for, such as telling them when the answer is published.

How do I stop the backlog from filling with junk?

Add a Captcha block to the form and filter obvious spam in the automation. If volume grows, use AI triage priority and category so low-value submissions land in Notion with a different status, or skip the card entirely.

Does one form per channel work better than one form with a source field?

One form with a hidden source field is easier to maintain. You edit the questions once, and every card still records its origin.

Next step: create the Notion database with the six properties above, share it with an integration, then build the form and send one test submission through the webhook before you post the link anywhere.