G2

Pim R.

WordPress developer

Small-Business (50 or fewer emp.)

11/4/2026

"Great visual automation for a small shop, but polling costs add up"

4.5/5

What do you like best about Make?

I run a small WordPress/WooCommerce site that sells digital Google Maps products, and Make is the backbone of our automation. The visual scenario builder makes even complex logic easy to follow. Our order-fulfilment scenario uses a router with separate paths for map products and regular Drive products: it shares the right Google Drive file with the buyer, logs the order in Google Sheets and sends a confirmation email. It has run almost 2,900 times since March with a single error, so I no longer have to check on it.

The native modules for WooCommerce, Google Drive, Google Sheets and Google Search Console cover nearly everything I need. When an option is missing, the "Make an API call" module lets me call the API directly, which I used for custom Search Console queries. The execution history and the per-module data inspection make debugging fast. I could also connect an AI model to the same scenarios, for example to turn Search Console data into monthly content suggestions.

As a one-person team without a developer, I could connect WordPress, Google Workspace and an AI API without writing a backend, and the pricing is friendly for a small business. Review collected by and hosted on G2.com.

What do you dislike about Make?

Polling triggers use up operations. Our "Watch Orders" scenario for WooCommerce checks every 15 minutes, so most of the operations are spent when nothing has happened. A native instant trigger for WooCommerce would be a big improvement, and a webhook is only a workaround.

Importing a scenario from a blueprint JSON was fragile. My import failed because some module names are still the old Integromat names, and I had to rebuild the scenario by hand with the current modules.

Mapping lists of key/value data, such as WooCommerce meta data, is easy to get wrong. Position-based access breaks as soon as the order of the items changes. You have to use first(map(...)) with the key name, and that is not obvious from the interface.

A scenario connected to WooCommerce kept deactivating after connection timeouts. I had to build a separate "watchdog" scenario that reactivates it. Better built-in retry behaviour or alerting would make that unnecessary. Review collected by and hosted on G2.com.

What problems is Make solving and how is that benefiting you?

Make removes manual admin from a one-person web business. It solves three problems for us:

1. Order fulfilment. Buyers of our digital Google Maps products get access automatically after payment. A router handles the different product types, the right Google Drive file is shared with the buyer, the order is logged in Google Sheets and a confirmation email goes out. Customers receive their product without delay, and I no longer have to process orders by hand.

2. Review requests. A scheduled scenario reads recent orders from a Google Sheet and sends a review reminder at the right moment, so we collect customer feedback without chasing anyone.

3. SEO and content maintenance. A monthly scenario pulls Search Console data and sends it to an AI model, which returns content-refresh suggestions in a Google Sheet. Another scenario is triggered by a webhook from WordPress when a new post is published and emails me internal-link suggestions. This gives me a repeatable review process for the site instead of a task I keep postponing.

Because I have no developer team, being able to connect WordPress, Google Workspace and an AI API in one visual tool is the main benefit. Review collected by and hosted on G2.com.