Wiring up a personal assistant with no-code tools

1. Know your starting point (and what we’re actually building)

If you’ve never built a Zapier “Zap” or a Make Scenario, you’re in the right place. We’ll stay on the shallow end: no code, no APIs, no custom webhooks.

You only need to be comfortable with:

• Signing up for websites and granting apps access to your Google account

If even that feels heavy, slow down and do this in two sessions. The first to wire it up, the second to test and fix.

The automation we’ll build:

Goal: Whenever you label an email as a receipt in Gmail, a new row appears in a Google Sheet with date, vendor, amount, and a link back to the email.

This is basic personal automation: boring, repeatable, and saves you minutes every week without drama.

2. Pick a first task that’s small enough to ship

Most people start too big. “Automate my whole life” dies in a maze of half‑connected tools.

Your first task should be:

Forwarding receipts to a spreadsheet hits all three. You already get receipts, they pile up, and a sheet is easy to scan.

If you don’t use Gmail or Google Sheets, you can adapt this later to Outlook + Excel Online or similar. For now, read through with the default stack so you get the mental model.

3. Tools you’ll use (without the hype)

We’ll use Zapier for the walkthrough because its free tier and UI are friendlier for a first build than most alternatives.

Here’s the only comparison you need today:

You’ll need:

No credit card, no paid plans, no enterprise OAuth headaches.

4. Design the workflow in plain language first

Before you click anything, write the workflow in words. That’s your guardrail against getting lost in menus.

We want:

That’s the trigger / action model you’ll reuse everywhere:

Trigger

What event starts the automation. One clear, specific change in a tool (a new email, a new row, a status update).

Action

What the automation does in response. Creating, updating, or sending something in another (or the same) tool.

Filter (optional)

A gate in the middle that decides “run or stop” based on conditions (subject line, sender, amount found, etc.).

Treat the plain-language version as your spec. If you can’t describe your automation in one trigger and one action, it’s probably too big for a first build.

Now we’ll translate that spec into a Zap.

5. Click‑by‑click: build the Zapier version

Work through this once without worrying about perfection. You’ll tighten it later.

5.1 Prepare Gmail and Sheets

1. Create a Gmail label called Receipts (Settings → Labels → Create new label).
2. Create a Google Sheet called Receipts Log with a header row:
   • A: Date
   • B: Vendor
   • C: Amount
   • D: Email Subject
   • E: From
   • F: Email Link

Leave the rest blank.

5.2 Create the Zap

Step 1: Trigger (Gmail)

1. 1

   For the trigger app, choose Gmail

2. 2

   For the event, pick New Labeled Email

3. 3

   Connect your Google account when prompted

   Grant read access.
4. 4

   Under Label/Mailbox, select Receipts

5. 5

   Click Test trigger

Zapier will look for a recent email with that label. If it finds none, go label one manually (grab an old receipt, apply the label, wait 10-20 seconds, then test again).

Step 2: Action (Google Sheets)

1. 1

   Click + to add an action

2. 2

   Choose Google Sheets

3. 3

   For the event, select Create Spreadsheet Row

4. 4

   Connect the same Google account

5. 5

   Choose your Spreadsheet

   Receipts Log.
6. 6

   Choose Worksheet

   usually Sheet1 unless you renamed it.

Zapier will show fields matching your header row. Map them:

Click Continue, then Test step.

If it works, Zapier should write one new row into Receipts Log using your sample email.

Finally, click Publish or Turn on Zap.

You now have a crude but working personal assistant.

6. Test safely (without wrecking your inbox)

You’re not done when Zapier says “success.” You’re done when you’ve watched it behave like it will in real life.

The main risk here: your trigger is too broad and starts grabbing unrelated emails.

Use a safe test pattern:

1. 1
   Create 3-5 fake test emails. Send yourself emails with subjects like Test receipt 1 - $12.34 from another account.
2. 2

   Label only these with Receipts

3. 3

   Wait 1-2 minutes and watch the sheet

You should see exactly one new row per labeled email. Nothing else should appear.

If you want to go one step safer, temporarily set the Gmail trigger’s Search String (advanced option in Zapier) to something like label:Receipts subject:"Test receipt". That keeps the Zap blind to real receipts until you’re happy.

7. Read the signals: did it actually work?

Automations don’t “work” or “fail” in a binary way. They give you signals.

For this Zap, watch for:

• Rows appear within ~60 seconds of labeling a test email → timing is fine.
• Each labeled email creates exactly one row → no duplicates, no misses.
• Columns look sane: dates in the right column, a recognizable vendor, subject, and a clickable link that opens Gmail.

Bad signals:

Check Zapier’s Zap History. Each run will show success or an error, with the data passed through. That’s your black box opened.

Don’t guess. When you’re not sure what happened, open the run log and read the actual input and output. A five‑minute look at real data beats half an hour of speculative clicking around settings.

Use these signals to decide your next move: tighten, fix, or leave it alone.

8. Tighten the workflow: filters and less noise

Right now, any email you label Receipts will be logged. That might be good enough. If not, add one filter.

In your Zap:

Now, even if you accidentally label a non‑receipt email, it won’t hit the sheet.

You can get fancier later (filters by sender like from:uber.com, from:amazon.com), but keep version 1 simple. Every extra condition is another way for things to silently stop working later.

9. When it breaks: simple debugging moves

At some point, something will break. The cost isn’t just fixing it; it’s noticing in time.

Here’s a small symptom → next step table you can use for this and future automations:

Zapier’s Task History shows each run’s data. Open a bad run, scroll through the Data In and Data Out, and compare it to what you expected.

If you can read those two blocks, you can debug 80% of beginner issues; no JSON knowledge required yet.

10. Planning your next automations (without overbuilding)

Once this is stable for a week, you’ll start seeing other candidates everywhere. Resist the urge to wire up everything.

A simple pattern for choosing the next one:

1. 1
   Count occurrences. Anything you do manually 10+ times a month is a candidate.
2. 2
   Check structure. The task should have clear inputs and outputs (form → sheet, calendar → Slack, etc.).
3. 3
   Keep one trigger, one main action. You can bolt on filters or an extra notification, but avoid branching logic on day two.

Examples that fit:

Each one reuses the same pattern you just learned: trigger, optional filter, action, safe testing, watch the logs.