Zapier · sdk · fg-0381
Zapier 'Updated record' polling trigger never fires for edits to existing records
New records trigger the Zap, edits to them never do
Verified 2026-10-15 · Confirmed by 0 builders · Trust 50/100
Cause
Polling triggers dedupe on the primary key, which is id by default. An edited record keeps its id, so Zapier treats it as already seen.
Fix
Make the primary key combine the id with the update timestamp, using primary in outputFields on platform-core 15.6.0 or later.
Apply
outputFields: [
{ key: 'id', primary: true },
{ key: 'updated_at', primary: true },
]Affects: Zapier Platform CLI polling triggers, primary keys from zapier-platform-core 15.6.0, as of 2026-10
Sources
- https://docs.zapier.com/platform/build/deduplication
- https://docs.zapier.com/platform/reference/cli-docs
Have your agent know this before it fails
claude mcp add --transport http footgun https://getfootgun.com/api/mcp