Look up user records and update downstream steps

A poster used a Zapier agent to find user records and update later steps, but it failed when source data had latency or formatting mismatches.

What They Did

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, using 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.

How It Went

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. The poster says Agents were still in beta yet had cost $400, and support confirmed at least one behavior looked like a bug.

Worth Knowing

The biggest catch was data matching: because Stripe-fed emails kept original casing, even simple user lookup broke unless the tool could search case-insensitively or the data was normalized first.