Send WordPress Form Submissions to a Notion Database

Notion has become the default lightweight CRM and ops hub for small teams because it blends a database, a wiki, and a project board in one workspace. The wider CRM market reached roughly $73.4 billion in 2024 and is projected to hit about $163.16 billion by 2030 at a 14.6% CAGR (Grand View Research, 2024).

Not every team needs Salesforce. A consultant tracking 40 leads, an agency managing client intake, or a startup logging demo requests often just wants a clean Notion table with a status column, an owner, and a follow-up date.

The problem is getting form data into Notion. People retype submissions by hand, paste from email, or wire up a brittle automation. SheetLink Forms removes that step entirely by writing each submission into your Notion database the moment it lands.

SheetLink writes submissions to Notion through a direct API integration, with no Zapier or Make in the middle. The Notion destination ships in the Integrations Bundle add-on, which also unlocks Airtable and five extra form plugins. There are no per-task fees, ever.

The flow is simple. A visitor submits one of your WordPress forms. SheetLink captures the fields, maps them to your Notion database properties, and creates a new page (row) in that database within a second or two.

Because it's a first-class destination, the same submission can land in Notion and Google Sheets at once. Many teams keep Sheets as the raw archive and use Notion as the working board. You configure both destinations on one rule, so you never duplicate setup or pay twice for the same lead.

Smart property mapping matches each form field to the correct Notion property type so your database stays clean and filterable. Notion is strict about types: a Date column rejects plain text, and a Select column expects defined options. SheetLink converts values to the right shape automatically.

Notion supports many property types, and SheetLink maps the common ones for form data:

- Title: the primary column, often the lead's name. - Email and Phone: typed fields that stay clickable. - Rich Text: longer message or notes fields. - Select / Multi-select: dropdown and checkbox answers become tags. - Date: submission timestamps and requested dates. - Number: budget, quantity, or score fields. - URL: a website field or a captured landing-page link.

This matters because a misaligned type means a broken database. In our experience, the difference between a Notion CRM people actually use and one they abandon is whether the Status, Date, and Owner columns are real properties you can filter and sort - not free text. Mapping at the source keeps every row queryable from day one.

Yes. SheetLink captures UTM parameters and ad click IDs automatically and writes them into your Notion properties alongside the form fields. Capturing the Google Click ID with each lead is exactly how you attribute and import offline conversions back to the campaign that produced them (Google Ads Help).

The plugin records GCLID, fbclid, and msclkid plus the standard UTM source, medium, and campaign values. You map them to Number, Rich Text, or URL properties just like any other field.

This turns a plain Notion intake table into an attribution-aware board. You can see which campaign produced each lead, filter by source, and later push that click ID back to Google Ads as an offline conversion. We cover the full setup in our UTM and GCLID attribution guide.

SheetLink protects every submission with a built-in retry queue, so a Notion API hiccup never loses a lead. If a write fails, the plugin queues it locally and retries with exponential backoff at 5 minutes, 30 minutes, and 2 hours until it succeeds, then logs the result.

This matters because hosted automation tools store your in-flight data on their infrastructure during an outage. With a direct plugin, the queue lives in your WordPress site and you keep full delivery logs.

The reliability gap is the real reason direct delivery beats hand entry and brittle automations. A lead that fails silently is a lead you never follow up on, and given how rarely teams hit the 5-minute response window already (Workato, 2020), you cannot afford a delivery path that drops records. Local queuing plus automatic retries means the row reaches Notion even if the API blinks.