Integration · 5 min read

Connecting the systems you already use, without polling

An automation is only as quick as the moment it hears about an event. Systems like Chatwoot, GitHub, Stripe and Shopify sign their webhooks, so MadeEasy hears the moment something happens, and can prove it came from them.

11 November 2026 · By Micheal Akinkuotu, Founder

There are two ways for an automation platform to learn that something happened in another system. It can ask, over and over (polling), or the other system can tell it straight away (a webhook). Polling is simple and it works for a few processes. It does not scale: every process asks every few minutes whether or not anything happened, and the answer always arrives late.

What a signed webhook is

When a system sends a webhook, it can also send a signature: a code worked out from the message and a secret that only it and the receiver know. The receiver works out the same code from what arrived. If they match, the message came from the system that holds the secret and was not changed on the way. Many systems also sign the time they sent it, so a copied message cannot be sent again later.

How MadeEasy checks it

  1. The request arrives at the process's own address.
  2. MadeEasy recomputes the signature over exactly what that system signs and compares it with what was sent, in a way that gives nothing away to someone guessing.
  3. A send time too far from now is refused.
  4. The system's delivery id is kept, so a delivery the system retries starts nothing the second time.
  5. Only then is the message read, and the process starts.

One checker, many systems

Systems sign in only a few ways: the message alone, the time and the message, or an id, the time and the message, written in hex or base64 in a header of their choice. MadeEasy keeps a shared list of senders that describes how each one does it. Today it holds Chatwoot, GitHub, Shopify, Stripe, the open Standard Webhooks specification (which many products follow) and a generic signed sender. Adding another is a new entry in that list, available to every process at once, with no new code and no release.

Everything particular to one system stays in the process that uses it: reading its messages, replying through its API, and ignoring its echo of your own replies. The platform itself knows nothing about Chatwoot.

Where the secret lives

The shared secret is kept in the process's own secret store and never shown again. You paste it once, on the process's settings page. The process's assistant can set up the connection when you ask ("connect this to Chatwoot"), but it never takes the secret in a chat: that stays on the settings page, where it belongs.

See it in action

The Chatwoot support triage runs on exactly this: every customer message reaches MadeEasy signed, the moment it is sent.

Bring the system your processes need to hear from

Tell us what it is and how it sends events. If it signs them, MadeEasy can listen today.