Hey Zapier! Stop introducing breaking changes into your integrations without deprecation warnings. Follow semver like normal people, or at the very least, publish a release strategy.
Sincerely,
A former consultant who hard sold like 50 of your customers to drop your platform after your last HubSpot integration debacle.
I don't know the inner workings of their deployment strategy, just that we couldn't trust the platform not to break in prod. And breaking the sales team workflow in prod is a high-visibility failure.
I guess I should be thanking them, because I upsold a chunk of those clients on custom development under the logic of "if you can't trust your middleware not to break, you need to own the middleware." But if the release strategy is coordinated solely by a single app developer, that would explain why they couldn't trust Zapier as middleware, I suppose.
Comments
Hey Zapier! Stop introducing breaking changes into your integrations without deprecation warnings. Follow semver like normal people, or at the very least, publish a release strategy.
Sincerely,
A former consultant who hard sold like 50 of your customers to drop your platform after your last HubSpot integration debacle.
Aren't most integrations on Zapier made by the apps themselves - aka HubSpot push updates to their Zapier app and fix anything which breaks.
I don't know the inner workings of their deployment strategy, just that we couldn't trust the platform not to break in prod. And breaking the sales team workflow in prod is a high-visibility failure.
I guess I should be thanking them, because I upsold a chunk of those clients on custom development under the logic of "if you can't trust your middleware not to break, you need to own the middleware." But if the release strategy is coordinated solely by a single app developer, that would explain why they couldn't trust Zapier as middleware, I suppose.