Zapier Zaps and Tables

Why it matters: Zapier is often the first automation tool a small team adopts. Used well it's fast; used carelessly it creates duplicate records and unowned data stores.

By the end you can:

• Build a trigger → action Zap on paper
• Use filters and paths correctly
• Decide what a Zapier Table is for
• Test for duplicates

Learn (15 min)

1. The basic shape (5 min)

A Zap begins with a trigger (app + event) followed by actions. Pick the exact event: "New Row" and "Updated Row" behave differently. Test with a real sample record so mapped fields show real values.

2. Control the path (5 min)

• Filter: continue only if conditions are met (e.g., consent = true).
• Paths: branch into separate action sequences (team vs. individual inquiries). Test both the matching and non-matching case, and decide what happens to records that match no path.

3. Tables and data lifecycle (5 min)

Zapier Tables can store records your Zaps use. Decide: is this a temporary handoff, a lightweight working list, or a source of truth? Define who can view and edit, how duplicates are detected (a unique key such as email), and how old rows are retained or removed. Don't store sensitive data without a purpose and an access plan.

Apply (15 min)

Worked example (3 min).

Trigger:  Website form submission
Filter:   consent = true
Action 1: Tables → Find record by email
Paths:    Found → Update record      | Not found → Create record
Path A (service = Team): CRM deal in "Corporate" + notify sales
Path B (service = Individual): booking-link email
Failure owner: Ops lead (Zapier error email + weekly review)

Lab (7 min): Duplicate-proof your Zap.

1. Design a Zap for a form-to-CRM flow.
2. Name the unique key you will search on, and what happens when the same person submits twice.
3. Create a test list of 5 submissions including two duplicates and one without consent.
4. Predict the final table/CRM state.

Deliverable: A Zap sketch and a predicted outcome table. You're done when: No duplicate contact appears in your prediction.

Check yourself (5 min)

1. What begins a Zap?
2. Filter vs. Paths?
3. Scenario: A Table is used by three Zaps and two people edit it manually. What governance questions come up?
4. How do you reduce duplicates?
5. Why test the non-matching branch?

Reference

Common mistakes

Cheat sheet: Trigger → test sample → map → filter/paths → verify destination → assign owner.

Key terms: Zap, trigger, action, filter, path, Table.

Interview prompts: How would you design a duplicate-safe lead Zap?

Go deeper: Set up a Zap action · Filter and path rules · Zap editor

Next: Lesson 15 — APIs, the layer under every automation tool.