Make, Zapier and n8n automations for WordPress and WooCommerce

An order comes in to WooCommerce, someone types it into the accounting software by hand, e-mails the courier and posts it in Slack. A form enquiry lands in an inbox and reaches the Google Sheet only when somebody remembers. These repeating steps can run on their own. We connect your WordPress site or WooCommerce shop to the other tools you use through Make (formerly Integromat), Zapier or an n8n instance installed on your own server, so the data moves by itself and you can see in a log what happened.

Typical flows: a form submission to Google Sheets, Slack or the right person’s e-mail; a new order to accounting, the CRM, the courier or a Telegram channel; stock and price updates from a spreadsheet into the shop; a weekly sales report; an abandoned-cart reminder or a review request after delivery.

What the work includes

• Choosing the platform. Make and Zapier are hosted services that are quick to start with, but the monthly fee grows with the number of operations. n8n we install on your server; it suits high volumes or cases where the data has to stay on your own infrastructure. We recommend one after reviewing your situation.
• Webhooks from WooCommerce and forms. We set up WooCommerce’s built-in webhooks for order, product and customer events and a webhook from your form plugin, so the data reaches the automation platform the moment it happens rather than on a polling schedule.
• WooCommerce REST API keys. Where a scenario has to read from or write to the shop, we create a dedicated API key with minimal rights: read-only when nothing is written, and a separate key for each scenario so one can be revoked without breaking the rest.
• Scenario building and field mapping. We build the flows module by module and map which order or form field goes into which field of the target system, converting dates, amounts and VAT into the format the target expects.
• Error handling and retries. If the target system’s API does not respond, the operation waits and is retried; a persistent failure sends you a notification instead of disappearing quietly. We also guard against duplicates when the same webhook arrives twice.
• Scheduled flows. Reports, stock updates and reminders run on the platform’s own scheduler rather than WP-Cron, which depends on someone visiting the site.
• A test run with real data. We place test orders and fill in the forms ourselves and check that the data arrives in the right place in the right shape before the flow is switched on for real.
• Documentation. We describe each scenario: what triggers it, what it does and where to change it. You can later adjust fields or destinations yourself without involving us.

Typical situations

A small shop gets a couple of dozen orders a day and the owner wants every new order to appear in a Telegram channel and go to the courier’s system without anyone clicking in the shop admin. A service company has three forms and every enquiry has to reach a Google Sheet and the Slack channel where sales discusses it. A wholesaler keeps prices and stock in a Google Sheet and wants changes to reach the shop on their own instead of being copied product by product. Or the Zapier flows already exist but break every week, nobody knows why, and orders go unrecorded in accounting.

What we need from you

• WordPress administrator access; for n8n, also access to the server or the hosting control panel.
• A Make or Zapier account in your name, or the decision that we install n8n on your server.
• Access to the target systems: Google account, Slack or Telegram workspace, API key for the accounting or CRM software.
• A description of what should happen: which event starts the flow, where the data goes and which fields matter.
• A test order or enquiry we can run the flows with.

What is not included

• The monthly fees for Make, Zapier or the server running n8n are yours; we help estimate which plan your volumes fit into.
• Complex two-way syncs where both systems edit the same records are often better built as a custom integration directly in WordPress, and we say so before starting.
• A full CRM or accounting integration with customer and product register sync: see CRM integration and SmartAccounts integration.
• Configuring the target systems themselves, such as creating Slack channels or the chart of accounts in the accounting software.

Who it suits

It suits a shop or service business where the same data is moved by hand from one system to another every day and where the volumes are such that a hosted platform’s monthly fee is less than the working time it saves. If the flows also need to write or classify text, for example drafting a reply to an enquiry, see AI automation. If you need continuous, reliable two-way synchronisation between two systems, that is a job for a custom integration rather than an automation platform.