Documentation

Everything you need to set up, run, and troubleshoot a connector.

How it works

A connector is a pairing of one source (the service sending events — Stripe, Shopify, GitHub, and so on) and one destination (where you want to see them — Discord, Slack, Google Sheets, or any URL you control). Creating a connector gives you a unique webhook URL:

https://zestyglue.com/hooks/{connector_id}

Paste that URL into your source service's webhook settings. From then on, every event that source sends is:

Verified — if the source supports a signing secret or token, ZestyGlue checks it with a timing-safe comparison before doing anything else with the request.
Normalized — the source-specific payload is turned into a common shape (title, a few summary lines, a footer) so every destination can render it sensibly.
Delivered — forwarded to your destination, and logged in your connector's event log (last 200 events, with status and any error message).

Getting started

Create an account — 14-day free trial, no credit card required.
Pick a source and a destination in the setup wizard, and fill in whatever credentials each one needs (a signing secret, a webhook URL, an API token — the wizard tells you exactly what's required and where to find it).
Copy your connector's webhook URL into the source service's own webhook settings.
Send a test event from the source (most have a "send test webhook" button) and check your connector's event log to confirm it arrived.

Every one of the pre-built connector pairing pages also has its own two-minute setup walkthrough specific to that exact source/destination combination.

Sources & destinations

Loading the current catalog…

Any source pairs with any destination — see the full browsable catalog for every combination, or use the setup wizard after signing up.

Billing & trials

Each connector is $9/month, billed as its own independent Stripe subscription, with a 14-day free trial that starts the moment you complete checkout — no credit card needed just to try a connector out.

Manage or cancel anytime from Dashboard → Manage billing, which opens Stripe's Customer Portal.
Deleting a connector cancels its subscription immediately — you're never billed for a connector that no longer exists.
If a subscription lapses (payment fails, or a trial ends without checkout), the connector is deactivated. Its source keeps getting a normal 200 OK response — it never sees an error or gets flagged — but events silently stop being delivered until you resubscribe.

Security & auth

Credentials you enter for a connector (signing secrets, webhook URLs, API tokens) are encrypted at rest and never displayed again after you save them — only a masked placeholder is shown.
Sign-in is email/password or Google Sign-In, with optional TOTP two-factor authentication (with one-time backup codes) layered on top of either.
Signature verification uses each source's own signing scheme (HMAC-SHA256 for most, with a couple of sources using SHA1 or MD5 because that's genuinely what they specify) with timing-safe comparison throughout.

Rate limits

Each connector accepts up to 60 requests per minute. Traffic beyond that is dropped (with a normal 200 OK response, same as any other silently-handled case) rather than queued or retried.

Troubleshooting

My source shows the webhook as delivered, but nothing shows up in my destination.

Open the connector's detail page and check its event log. rejected usually means signature verification failed (double-check the secret matches on both sides); failed means the destination itself returned an error (check that a webhook URL or token is still valid); inactive means the connector's subscription isn't active.

Why doesn't my source ever show a webhook delivery failure, even when something's wrong?

By design. ZestyGlue always returns 200 OK to the source, whatever actually happened — many source services retry aggressively (or disable a webhook entirely) after repeated errors, so problems are surfaced only in your ZestyGlue event log, never as retries or alarms on the source's side.

Can I change a connector's source or destination credentials after creating it?

You can rename a connector at any time. To change its credentials, source, or destination, delete it and create a new one — the wizard takes about two minutes.

Can I see the raw payload a source actually sent?

The event log keeps a 200-character preview of each event's payload, alongside its type, status, and any error message.

I don't see the connector or destination I need.

Any source can already pair with the generic "Any Webhook" source or "Custom Webhook" destination if there's no dedicated adapter yet. For anything more specific, use the feature request board — that's exactly what it's for.

Feature requests

Want a new source, a new destination, or a change to how something works? Post it (or upvote an existing one) on the feature request board. There's no support ticket queue here — that board is genuinely how priorities get decided.

Still stuck? Email [email protected].