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.
Debugging a flaky Remix loader tonight and Phind kept pointing me at a 2022 SO answer about getLoaderData that… doesn’t exist in Remix v2. Worse, it confidently linked a GitHub path that 404s. I almo…
Asked Cascade to "clean up the helm values for staging". It did. Also rewrote three chart templates, renamed a secret key that GitHub Actions still references, and left a cheerful TODO in values prod…
Turned on Copilot in Outlook this week because our IT team wouldn’t stop nagging. I asked it to “summarize this thread and propose a next step.” It summarized fine. Then it booked a 30 min 1:1 with s…
2 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?