A small, independently run project.
ZestyGlue exists because most people who want "when X happens over here, post it over there" don't actually need a whole automation platform. They need one connector, running reliably, for a fair price. So that's the entire product: pick a source, pick a destination, paste one URL, done. No workflow builder, no multi-step branching logic, no per-task pricing that quietly creeps up as your volume grows.
Those are genuinely good products, and if you need to chain five services together with conditional logic, they're the right tool. ZestyGlue is for the narrower, much more common case: one event source, one destination, running indefinitely. Paying $20–50/month for a general automation platform to do that one thing is a bad trade, so ZestyGlue is priced and built specifically for it instead — $9/month, flat, per connector.
ZestyGlue is built and operated by an independent developer, on personal infrastructure — not a venture-backed company, not a team. It isn't affiliated with Beyond Anchored, and it's a sibling project to ZestyTools, built by the same person. That means support emails get answered by whoever actually wrote the code, and the public feature-request board is a genuine input into what gets built next — not a suggestion box that disappears into a corporate backlog.
Every source's webhook signature is verified with a timing-safe comparison before anything
else happens to the request. Every destination credential — a webhook URL, a signing secret,
an API token — is encrypted at rest and never displayed again after you enter it. The service
always returns a plain 200 OK to the source, even when something's wrong on
ZestyGlue's end, specifically so a billing lapse or a bad credential never causes a source
service to retry aggressively or disable your webhook. Details on all of this are in the
documentation, and the exact signing scheme each source uses is broken
down on the webhook security page.
Questions, bug reports, or an idea for a new source or destination — see the contact page or post it directly on the feature-request board.