Automate the boring stuff with Zapier or Make

There is a category of work in every office that a computer should be doing: copying form responses into a spreadsheet, emailing people when a row changes, saving invoice attachments into the right folder. Nobody was hired to do this. Everybody does some of it anyway. Zapier and Make exist to take it off your plate, and you do not need a developer to use either one. In this guide we will build your first three automations and show you when Make is worth the switch.

By the end you will have three working automations: a form that files its own responses, a spreadsheet that sends its own notification, and invoices that save themselves into a folder. More importantly you will know the trigger and action model, which is the whole mental model for both tools.

Prerequisites

• A Zapier account. The free tier handles two-step automations, which covers everything in this guide. Paid plans start around twenty to thirty dollars a month.
• Accounts for the apps you are connecting. We will use Google Forms, Google Sheets, Gmail, and Google Drive, but the same recipes work with Microsoft Forms, Excel Online, Outlook, and OneDrive. Swap in your stack.
• A real form and a real spreadsheet to test with. Made-up test data is fine; made-up test apps are not.

Step 1: Learn the trigger/action model

Every automation in Zapier (a "Zap") has the same shape: one trigger and one or more actions. The trigger is the event Zapier watches for: a new form response, a new email, a new row. The actions are what happens next: create a row, send an email, save a file. Data flows downhill; anything the trigger captures (the form answers, the email attachment) can be mapped into any field of any action after it.

That is the whole model. Make calls the same things "modules" in a "scenario," and every other automation tool uses some version of it. Once you can say "when X happens, do Y with the data from X," you can build in any of them.

Step 2: Zap one, form to sheet

The classic starter: new form submissions land in a spreadsheet automatically, so nobody exports CSVs on Friday.

1. In Zapier, click Create Zap.
2. For the trigger, choose the Google Forms app and the New Form Response event. Connect your Google account when prompted and pick your form.
3. Click Test trigger. Zapier pulls in a recent real response so you can see the actual fields. Always do this; mapping against real data is how you catch that the form calls it "Full name" while you expected "Name."
4. For the action, choose Google Sheets and the Create Spreadsheet Row event. Pick your spreadsheet and worksheet.
5. Zapier shows one field per column in your sheet. Click each field and map the matching piece of form data from the dropdown.
6. Test the action, check that the row appeared in your sheet, and turn the Zap on.

Step 3: Zap two, sheet to email

Now the reverse direction: when a row gets added (or updated to a certain status), someone gets told. Useful for lead notifications, order alerts, anything where a spreadsheet is quietly filling up and a human needs to react.

1. Create a new Zap. Trigger: Google Sheets, event New Spreadsheet Row. If you only care about rows that reach a certain state, use New or Updated Spreadsheet Row and set the trigger column to your Status column.
2. Action: Gmail, event Send Email. Put the recipient in To, then build the subject and body by mixing typed text with mapped fields: subject New lead: plus the Name field, body pulling in whatever the recipient needs to act without opening the sheet.
3. Test it, read the email you receive, and fix the wording before turning it on. Automated emails get sent a lot; a sloppy one gets sent a lot too.

One habit worth building here: filters. Click the + between trigger and action and add a Filter step, for example "only continue if Amount is greater than 500." Filters are how you keep automations from firing on everything.

Step 4: Zap three, invoice attachments to a folder

This one saves real time during month-end. Emails with invoice attachments get filed into a Drive folder automatically instead of living in someone's inbox.

1. In Gmail, create a label called Invoices and a Gmail filter that applies it, for example messages where the subject contains "invoice" or from your regular vendors. Doing the matching in Gmail keeps the Zap simple and cheap.
2. New Zap. Trigger: Gmail, event New Labeled Email, label Invoices.
3. Action: Google Drive, event Upload File. For the File field, map the email's Attachment. Pick the destination folder, something like Accounting/Invoices/Inbox, and let your bookkeeper sort from there.
4. Test with a real vendor email, confirm the PDF lands in the folder, turn it on.

Step 5: Test like it will break, because it will

Every Zap has a run log: open the Zap and check its history, or watch Zap Runs in the dashboard. After you turn anything on, feed it two or three real-world cases and read the log for each. The failures you will actually hit are boring ones: a renamed spreadsheet column, a Google password change that disconnects the account, a form field someone deleted. Turn on Zapier's error notification emails and actually read them, because a silently dead automation is worse than no automation. People assume it is working.

When Make wins

Zapier's edge is that every recipe above takes ten minutes and the interface never fights you. Make (formerly Integromat) wins in three situations.

First, price at volume. Both tools charge by usage, but Make's per-operation pricing is markedly cheaper once you are running thousands of runs a month. If your Zapier bill is creeping past a hundred dollars a month, price the same workload in Make; the difference is often severalfold.

Second, branching. Zapier is mostly a straight line with filters. Make's visual builder is a canvas where one trigger can fan out into multiple routes: invoice over 5,000 goes to the manager for approval, under 5,000 files straight to the folder, and anything from a new vendor also pings accounting. When you catch yourself building three near-identical Zaps to fake a branch, that is the sign.

Third, fiddly data. Make handles iteration over lists, JSON, and transformation steps more gracefully. If your automation needs to loop over line items, you will feel it.

Our honest advice: start in Zapier because you will actually finish. Move a workflow to Make when the bill or the branching demands it. And write down what each automation does and which account owns it, because a year from now, when a form quietly stops filing itself, someone needs to know where to look. If that someone should be us instead, that works too.