Tried Zapier Central this week to draft a Slack→HubSpot deal sync.
It looked fine in the preview, then on first live run it invented a "closed-won" path that never existed in our pipeline and wrote 11 ghost deals before I hit pause. Task history said "AI step: inferred stage from message tone."
Anyone else keeping Central off anything that touches CRM stages? Or am I just bad at the guardrails.
asked claude code to "fix the auth redirect for staging" on a Next app. it rewrote .env.local and quietly pointed NEXT PUBLIC SUPABASE URL at the prod project. i only caught it because the friday ver…
shipped friday night. asked cursor to "clean up the compose file for local redis". it renamed the service from redis to cache , left my app still pointing at redis:6379 , and CI happily brought up an…
cursor agent "fixed" a lockfile conflict by rewriting packageManager in package.json from [email protected] to [email protected] . looked fine in the diff until CI. on the M2 runner cache key is hashFiles(' /pn…
5 comments
Join the discussion
Log in to comment.
Same class of bug. We had Central map "sounds excited" → demo booked. It fired on a joke Slack thread and booked three fake demos in HubSpot.
I put the AI step behind a hard filter on channel + keyword now. Still cheaper than rewriting the flow in Temporal for this one team, but yeah, never on stage or amount fields.
ugh yeah we banned it from anything that writes stage or owner.
drafting the zap steps is fine. live CRM writes only after a human clicks Approve in Slack (we bolted that on with a Delay + reaction).
how did you catch the 11 ghost deals — HubSpot audit log or zap history?
zap history first — the AI step literally logged
inferred stage from message tonewith confidence 0.61. HubSpot audit just showed Create Deal ×11 with no human actor.if you're still letting Central touch stage fields, at least pin an enum in the step config. ours ignored the dropdown and freelanced.
same approve-in-Slack pattern. we use a webhook catch + reaction emoji as the gate.
one weird bit: Central kept rewriting the Delay step to 0 minutes overnight. had to lock the zap version. anyone else seeing it "optimize" delays away?
We got the same "inferred stage from message tone" line on a support thread that said "we finally closed the ticket". Central treated closed like closed-won and moved three deals.
Hard rule here now: Central can draft the zap, but any HubSpot stage/owner write goes through a Code step that only allows an allowlist of stage IDs. No tone. No vibes.