Want a reliable way to capture website data in a spreadsheet without manual copy/paste? This article shows exactly how to connect WordPress and Google Sheets with Make so form submissions, new posts, or user signups flow automatically into a sheet you control. I’ll give practical, step-by-step instructions, example workflows for solopreneurs, and common pitfalls to avoid.
Quick answer: two simple ways to connect WordPress and Google Sheets with Make
You can connect WordPress and Google Sheets in Make with either a dedicated WordPress module (uses the WordPress REST API) or by using a Make webhook that receives data from a form or custom code. Choose the WordPress module if you want Make to poll or interact directly with WordPress resources (posts, users, comments). Choose webhooks when you need immediate, push-style delivery from forms or custom site events.
When this integration is useful for one-person businesses
- Collect leads from a website form and log them to a Google Sheet for follow-up.
- Archive new blog posts, comments, or user registrations in a sheet for content planning or reporting.
- Combine WordPress form data with other apps (CRM, email, accounting) using Make’s visual scenario builder.
What you’ll need before you start
- A Make account (free tier works for testing; paid plans handle higher volumes).
- Access to your WordPress admin account. If using the WordPress module, you’ll need an account that can create an application password or install a lightweight connector plugin if your hosting blocks REST API access.
- A Google account and a Google Sheet ready to receive data (create column headers first).
- If using a form plugin (WPForms, Gravity Forms, Contact Form 7, etc.), the ability to send a webhook or custom POST on form submission.
High-level setup steps
- Create a new scenario in Make.
- Add a trigger: either Make’s WordPress module or a Webhooks module.
- Authenticate the WordPress or webhook source.
- Add a Google Sheets module to create or update rows.
- Map the fields (name, email, message, date, etc.), test with sample data, then activate the scenario.
Step-by-step guide: Option A — Use Make’s WordPress modules (poll or act on WP data)
Best for: syncing posts, comments, or users; automations that can run on a schedule or need to read/update WP content.
1. Prepare WordPress for API access
- Enable Application Passwords: in WordPress, open a user profile (usually your admin account) and create an Application Password. Copy it — you’ll use it for authentication in Make. Application Passwords are available in recent WordPress versions.
- If your site blocks the REST API or uses basic auth restrictions, talk to your host or install a secure connector plugin. Make requires REST access to interact with WordPress resources.
2. Create the scenario in Make
- Log in to Make and create a new scenario.
- Add the WordPress app as the trigger module — choose an action like “Watch Posts”, “Watch Users”, or “Watch Comments” depending on what you want to capture.
- When prompted, connect to your WordPress site. Use your site URL, your WordPress username, and the application password you created.
- Configure filters if you only want certain post types or statuses (for example, only “published” posts).
3. Add Google Sheets action
- Add the Google Sheets module and select “Create a Row” or “Update a Row”.
- Authenticate with your Google account when prompted (Make uses OAuth to access Sheets).
- Select the spreadsheet and worksheet. Make sure your spreadsheet has headers (e.g., Date, Name, Email, Content, Source).
- Map fields from the WordPress module to the sheet columns (post title → Title, post date → Date, author → Author, link → URL).
4. Test and activate
Run the scenario once with a recent post or user to verify the data lands correctly. Use Make’s execution log to inspect output and fix mapping or formatting issues. When satisfied, set the schedule or enable real-time watching and activate the scenario.
Step-by-step guide: Option B — Use a Make Webhook (push-based, best for forms)
Best for: immediate capture of form submissions, lead capture, or custom events that should be pushed to Make as they happen.
1. Create a webhook in Make
- In Make, add the “Webhooks” app and choose “Custom webhook”.
- Create a new webhook and copy the generated URL. This is the endpoint your WordPress form or custom code will POST to.
2. Send form data from WordPress
Three common approaches:
- Form plugin with webhook support: Many form plugins let you send form submissions to an external URL. Paste the Make webhook URL into the plugin’s webhook or web service integration setting.
- Use a form plugin’s Zapier/Make add-on (if available) to send submissions.
- Custom code: add a small function to your theme or a custom plugin that makes a POST request to the webhook URL on form submission. Ensure the request uses HTTPS and includes expected field names (name, email, message).
3. Add Google Sheets module
- After the webhook module in the scenario, add Google Sheets → “Create a Row”.
- Authenticate Google account and choose spreadsheet/worksheet.
- Map incoming webhook fields to the sheet columns. Add a timestamp or source label for clarity.
4. Test and refine
Submit the form and verify the row appears. Use Make’s scenario run history to debug missing fields or unexpected formats. Add validation steps or Slack/email notifications if a submission needs immediate human attention.
Example: Capture new leads from a contact form into Google Sheets
- Create a Google Sheet with headers: Timestamp, First Name, Last Name, Email, Source, Notes.
- In Make, create a webhook and connect your form plugin to that URL.
- Add a filter in Make to ignore test or spam submissions (e.g., reject if email field is empty).
- Add Google Sheets → Create a Row and map fields. Optionally add a second action to create a contact in your CRM or send a Slack message.
Comparison: WordPress module vs Webhook vs Form plugin add-on
| Method | Best for | Latency | Complexity | Notes |
|---|---|---|---|---|
| WordPress module | Syncing posts, users, comments; reading/updating WP content | Near real-time (polling interval) | Medium — requires REST/API access | Requires WP Application Password or connector; good for two-way actions |
| Webhook | Immediate form submission capture and push events | Real-time | Low to medium — depends on form/plugin or small code snippet | Fast and reliable for lead capture; ideal for low-latency needs |
| Form plugin add-on | Users of a specific form plugin who want an out-of-the-box integration | Real-time | Low — uses built-in plugin settings | Convenient but may require paid plugin features |
Practical tips and best practices
- Set clear spreadsheet headers before mapping fields. Changing headers later can break scenarios.
- Normalize timestamps in Make to one timezone so reporting is consistent.
- Protect PII: avoid logging sensitive data unless necessary and ensure your sheet’s sharing settings are secure.
- Test with real sample data and check Make’s execution log for parsing issues (empty fields, unexpected arrays).
- Deduplicate: add a lookup step in Make to avoid inserting duplicate leads (search the sheet for existing email before creating a row).
- Monitor usage: Make counts operations; if your site generates many events, batch them or apply filters to reduce runs.
- Use error handling: add a route for failed executions (send an email or Slack alert) and consider retries for temporary network failures.
Common mistakes and how to avoid them
- Authentication failures: double-check application passwords, OAuth consent, and that your WordPress site uses HTTPS.
- Wrong field names: webhooks send the exact parameter names the form uses—verify them in Make’s webhook sample data.
- Sheet access issues: confirm the Google account connected in Make has edit rights to the target spreadsheet.
- Hidden spreadsheet headers: inserting rows into the wrong sheet/worksheet is a common misstep—verify spreadsheet and worksheet IDs.
- High volume costs: Make counts operations; if you expect many form submissions, estimate monthly usage and choose a plan accordingly.
Related automations and next steps
Once your WordPress → Google Sheets flow is reliable, consider these practical expansions:
- Add a CRM step to convert sheet rows into contacts automatically.
- Trigger personalized emails or SMS follow-ups on new leads.
- Aggregate form responses into weekly reports or dashboards.
For more Make-focused idea starters, see 10 Make Automations for Freelancers. If your primary goal is capturing leads, this walkthrough pairs well with How to Automate Lead Capture from Your Website. If you’re weighing platform choices for automations, you might also find Make vs Zapier for Small Businesses useful.
Useful external references
- WordPress REST API documentation — how WordPress exposes content for external apps.
- Google Sheets API documentation — background on Sheets access and limits.
- Make (official site) — account setup, app modules, and help center.
Frequently asked questions
Will this work with any WordPress form plugin?
Most form plugins let you forward submissions via webhook or custom HTTP requests. If your plugin lacks that feature, check for an add-on or export capability, or use a lightweight custom code snippet to POST to a Make webhook.
Can I update an existing row instead of creating duplicates?
Yes. Use a Google Sheets “Search Rows” or “Get a Range” module in Make to check for existing records (matching email or ID) and then use “Update a Row” if a match is found. This is the standard deduplication pattern.
Is Google Sheets reliable long-term as a CRM or database?
Google Sheets is great for lightweight tracking and reporting. For more advanced CRM features (contact history, tasks, automation scalability), consider a dedicated CRM. See Guantech’s comparisons for context, including our article on CRMs and Sheets.
Conclusion — a practical first automation to try
Start simple: create a Google Sheet with clear headers, set up a Make webhook, and connect a single form to feed new leads into the sheet. Test thoroughly, add a dedupe check, and iterate by adding notifications or a CRM step. Connecting WordPress and Google Sheets with Make is an efficient way for solopreneurs to capture, organize, and act on web leads without manual data entry.

