webhooks.xyz
Compare / Make
webhooks.xyz vs Make
Visual automation (formerly Integromat) with custom webhooks and a scenario builder.
What Make does well
It detects the payload structure from a sample, lets you answer the caller, queues incoming calls, and costs less than Zapier per operation.
Where webhooks.xyz differs
- Make treats a webhook as the start of a scenario. webhooks.xyz treats it as the thing to inspect, verify, keep and deliver. There is no scenario to build for the common case.
- Signature verification and replay of failed deliveries are not built in to Make.
Pick Make when
You like visual flows and need to connect several apps with light logic.
Pick webhooks.xyz when
You receive webhooks from Stripe, GitHub, Shopify or any of 50+ providers and want to see, verify and deliver them reliably, for free, without building a workflow.
Feature by feature
| webhooks.xyz | Make | |
|---|---|---|
| Instant URL that shows requests | ● | ◐The webhook queue shows waiting calls. There is no request history view. |
| Mock responses | ● | ● |
| Signature verification | ● | – |
| Destinations with retries and replay | ●Free and Dev have the same retries and replay. Only retention differs. | ◐Incomplete executions can be stored and retried by hand. |
| Local tunnel (CLI) | ● | – |
| Failure alerts | ● | ◐ |
| Actions with your own keys | ● | ● |
| Full API | ● | ● |
| Inbound email parse | ● | ●Mailhook gives an address that triggers a scenario. |
| AI help on payloads | ●With your own key (Anthropic, OpenAI, Gemini, Mistral, Groq, OpenRouter): explain a request, write a handler, suggest a filter, summarise a day. | ◐ |
| AI parsing: turn a payload or a mail into fields | ◐The assistant reads a request or a mail and answers you. An AI step that writes fields into the pipeline for each request is not built yet. | ●AI modules and text parsers extract fields in a scenario. |
| Python or JavaScript post-processing | ◐JavaScript functions and JSONata expressions on routes, in a sandbox: 100 ms, 16 MB, no network. No Python and no containers yet. | ◐Custom code is limited to some plans and modules. Most logic uses built-in functions. |
| Multi-step workflows (like Zapier) | ◐In progress, off until you turn it on: a request starts steps (send, set, if, switch, foreach, wait, http, forward). No catalogue of app actions; connections and HTTP cover them. | ● |
| Import from other tools | ● | – |
| Private relay for closed networks | ●whx relay inside your network takes deliveries over one outbound connection. | – |
| Self-hostable | ○Coming soon: one container in your own cloud account, maintained by us (Business plan). | – |
| Free tier you can use for real | ●10 days of history and every feature with small limits. Dev has 30 days. | ◐ |
● yes ◐ partly or with caveats ○ coming soon here – no
Pricing
Free tier with 1,000 operations a month. Paid plans start at about $9–10 a month.
| Make plan | Price | Includes |
|---|---|---|
| Free | $0 | 1,000 operations a month, 2 active scenarios |
| Core | about $9–10 / month | 10,000 operations, unlimited scenarios |
| Pro and Teams | about $16–30 / month | More operations, priority execution |
| webhooks.xyz plan | Price | Includes |
|---|---|---|
| Free | $0, invite-only while in build | All free features, 24 hours of retention |
| Dev | 7-day trial, no card, then about $9 / month | The same features, 30 days of retention |
| Team, Business | coming soon | Transformations, SQL access, published views, SSO, self-hosted |
Use both
Put a bin in front of Make. The bin shows and verifies each request, keeps it, and forwards it. Make keeps doing what it does well.
Facts about Make come from its public docs and pricing pages as of 8 October 2026 (the rows on AI parsing, code and workflows: 15 October 2026). Found an error? Tell us, and we fix it. The webhooks.xyz column includes features that are in progress. The feature list shows what is live.