Free WPForms Spreadsheet Integration: Connect Google Sheets, Airtable, and More

The WPForms Google Sheets add-on requires the WPForms Pro or Elite plan. The WPForms Airtable add-on requires WPForms Elite.

The WPForms Notion add-on is available from Plus upward; it is worth checking first if a structured database rather than a spreadsheet would satisfy the requirement.

WPForms Lite and WPForms Basic include none of the three. A WPForms Lite user who wants submissions to reach Google Sheets or Airtable in real time without upgrading needs a separate connector plugin, because the plan tier gates the native add-ons.

Whether to upgrade WPForms or add a connector depends on how many other Pro or Elite features you would actually use.

WPForms spreadsheet integrations by plan

Spreadsheet and database destinations in WPForms are gated by plan tier, not by submission volume. All four paid plans include unlimited forms, submissions, and users. What changes is the feature set and the number of sites each licence covers: one on Basic, three on Plus, five on Pro, unlimited on Elite.

Last verified: August 2026, against the WPForms pricing page.

On price: WPForms lists Basic at $49.50, Plus at $99.50, Pro at $199.50, and Elite at $299.50 per year.

These are introductory prices at the time of verification, and the pricing page states renewals are charged at full price ($99, $199, $399, $599). Confirm figures before budgeting.

Four Ways to Get WPForms Data Into a Spreadsheet

Four routes exist. They differ in where processing happens, what the price attaches to, and how much logic each can apply en route.

Two trade-offs matter more than the rest.

The first is what the price attaches to. Native WPForms add-ons and integration plugins are licensed per site for a period of time, so what you pay does not move as submissions increase.

Zapier, Make, and n8n meter usage by task, so cost tracks volume. At a few dozen submissions a month, that gap is minor; at several thousand, it is not.

The second is capability. Cloud platforms can branch, filter, delay, look up a record elsewhere, and chain steps together.

A native add-on and an integration plugin both perform single-step delivery with conditional logic attached, which covers most spreadsheet workflows but not orchestration.

Manual export deserves naming rather than dismissing. For a form taking a few dozen entries a month that nobody needs to see immediately, a monthly export costs nothing.

Should you upgrade WPForms or use an integration plugin?

The answer turns on how much of the higher WPForms plan you would actually use, not on the spreadsheet. From WPForms Plus, moving to Pro is a one-tier upgrade and moving to Elite is a two-tier upgrade.

Upgrade WPForms when:

• You need several other features from the target plan: payments, calculations, conversational forms, or signatures on Pro; Salesforce, HubSpot, and webhooks on Elite.
• You want native setup in the form builder and one support provider for the whole path.
• You manage enough websites that the license makes sense on site count alone. Pro covers five sites, Elite unlimited with multisite support.
• Other integrations you need are already in that plan.

Consider the Integration plugin like Bit Integrations when:

• You use WPForms Lite, Basic, or Plus and need only one or two external destinations.
• Your destination is unavailable in your current plan, and nothing else in the higher plan is on your roadmap.
• You want workflows to run from WordPress without per-task cloud billing.
• You accept a second plugin and, for Google Sheets, a more involved one-time authentication step.

Use manual export when volume is genuinely low and the data is not time-sensitive. A monthly download is a legitimate answer, not a fallback.

Use a cloud automation platform when the workflow needs multi-step routing, branching, delays, record lookups, or orchestration across external applications that a single-step connector cannot provide.

The WPForms Zapier, Make, and n8n integrations are themselves Pro-tier, so this route does not avoid an upgrade.

Neither route is universally better. A Plus user who also wants payments should upgrade to Pro. A Lite user who wants one spreadsheet has a reasonable case for an integration plugin.

What to verify before choosing

A few details can change the decision after setup, and each is easier to check beforehand.

Whether records are created or updated. The WPForms Airtable add-on documentation states that a new record is created in the selected table each time the form is submitted and does not document updating existing records.

The WPForms pricing page uses looser marketing wording, so if updating an existing record is a hard requirement, confirm the behavior with WPForms support before buying Elite.

The Bit Integrations Airtable action is documented the same way, and the Google Sheets route appends a new row in both products.

Authentication and setup. Native WPForms add-ons authenticate inside the form builder in a few clicks.

The Bit Integrations Google Sheets action requires a one-time Google Cloud setup: create a project, enable the Google Sheets and Google Drive APIs, create an OAuth client, and then paste a Client ID and Client Secret into the plugin.

It happens once, but allow time for it. The Airtable action uses a personal access token instead.

Support responsibility. With a native WPForms add-on, one vendor sees both ends of the connection. With a connector or cloud service, diagnosis crosses a vendor boundary. If you maintain client sites under a response-time commitment, weigh this properly.

Where processing happens. A connector sends data from your own server. A cloud service adds a third party to the chain. Neither is automatically better, but the number of services touching a submission is worth counting when the data is sensitive.

Real WPForms Lite workflow with Bit Integrations

The workflow below is WPForms submission → Bit Integrations → Google Sheets or Airtable, running on WPForms Lite. Bit Integrations lists WPForms among the triggers in its free version, which is what makes the Lite case possible.

Step 1. Select WPForms as the trigger. Create an integration in Bit Integrations, choose WPForms from the trigger list, then select the form.

Step 2. Select the spreadsheet platform as the action. Choose Google Sheets or Airtable, then authorise. Google Sheets asks for a Client ID and Client Secret from your Google Cloud project; Airtable asks for a personal access token.

Step 3. Map form fields to destination columns. WPForms fields appear on one side, spreadsheet columns or Airtable fields on the other.

Step 4. Add conditional logic if needed, then test. Conditional logic is included in the free version and controls when the integration runs. A test submission confirms whether a new row or record is created, and the timeline logs success and error states.

See also the guide to automating WPForms entries and the free Google Sheets connector for WPForms.

Conclusion: Quick decision scenarios

For destinations beyond spreadsheets, the broader WPForms integrations guide covers CRM and email options, alongside free WPForms email marketing integration tools.

Frequently Asked Questions