When should you use it?
- Your agent finds customer records by email address
- Records come from payment or form tools
- Lookups miss existing users
Not for: Systems already enforcing normalized keys
What do you need, and what do you get?
You need
- Customer table
- Intake automation
You get
- Normalized key column
- Lookup tests
How does it work, step by step?
- Add a key columnStore lowercase, trimmed email at write time.
- BackfillNormalize existing rows.
- Lookup on the keyPoint agent tools at the normalized column.
- Normalize inputClean the email the agent searches with the same way.
- TestTry mixed-case and spaced inputs.
The prompt
Our own prompt, inspired by u/pottercron on r/zapier and written to work in Zapier, Make and n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Given this list of customer records {records}, normalize email (lowercase, trimmed) and phone (digits only with country code).
List records that collide after normalization as likely duplicates. Do not merge; report only.Inspired by u/pottercron on r/zapier: Issues With Zapier Agents. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Some agent tools cannot see new columns until refreshed; test after changes.
- Duplicates appear after normalization; merge them.
Our take
The frustration is with a specific tool, but the lesson travels: agents are only as good as the keys they search on. Normalizing at write time removes the problem for every tool downstream. Add a canonical key column, backfill it, and make lookups use that key only. Normalize input on every write path, including imports and admin edits. Test with deliberately weird casing and whitespace. Document the rule so future agents and humans do not invent new formats. Prefer email lowercasing and trimmed strings; for phones, store E.164. When a tool cannot normalize, refuse to use it for lookups until it can. Monitor failed lookup rates after the change. Keep a one-off repair script for historical rows. Never teach the agent to guess among near-matches for account changes without a human confirm. Audit admin emails that grant access after the migration. Add a unique constraint on the canonical key so duplicates cannot creep back in.
Where the time goes back: Agents stop creating duplicates or missing customers because of formatting.
FAQ
Why not rely on instructions?
Does it apply beyond email?
Source and credit
Inspired by u/pottercron on r/zapier. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Issues With Zapier Agents
- Creator
- u/pottercron on r/zapier
- Published on
- Original date
- Mar 6, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Zapier
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.