Look up user records and update downstream steps
Case study takeaway: the poster set up three Zapier agents for a subscription product: one to email admins a current user list, one to add users, and one to remove them, powered by a Zapier Table as the customer database. The agents looked up customers by the email Stripe had written into the table, then later needed to search by another field to find linked subaccounts; the person tried both changing the Find Records operator and adding a lowercase-normalized formula column, but hit bugs and missing-field issues. It never became reliable: case-sensitive lookups, inability to set the needed operator when multiple lookup fields were required, unseen new columns, and draft/version errors blocked the workflow.
- Agent or tool
- Zapier Agents
- Topic
- Automation
- Reported on
- Added
- 2026-10-15
Why it matters
Automation used to mean wiring up rigid rules. Agents can handle the messy, in-between steps that rules miss, which makes many more workflows worth automating. It is one of 19 sightings filed under Automation on Agent Sightings (number 2 by interest), and one of 7 involving Zapier Agents.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Zapier Agents or any similar agent and adjust the details to your situation.
Automation design: look up user records and update downstream steps. Specify triggers, steps, and failure modes before enabling sends or deletes.
Tip: Start small: run it once on a low-stakes example, read what the agent did, and only then let it run on real work.
Source
Read the original first-hand account on Reddit: https://www.reddit.com/r/zapier/comments/1rmgfwu/issues_with_zapier_agents. Our summary is a paraphrase; details are in the source.