Webhook infrastructure

Receive the webhook.
Then actually do something with it.

Idempotency, retries and a dead-letter queue on the way in. A canvas of typed nodes on the way out.

Create an endpoint See the flows

No credit card. Your first endpoint is live in about ten seconds.

Talks to what you already use

Google SheetsGmailSlackNotionShopifyGitHubStripeJiraDiscordTelegramPostgreSQLMongoDB

On the way in

An endpoint that tells you the truth

Three states, and you can open every one of them.

delivered

Deduplicated and dispatched. The run keeps its payload, so you can open it a week later.

retrying

Attempts and delay are yours to set per endpoint — not a policy you inherit.

dead-letter

It waits with its reason and its body. Fix the cause, send it again.

A repeat has to say it is one: an Idempotency-Key, the provider’s delivery id, or an id in the body.

What people build

Flows, drawn the way the canvas draws them

Not a picture of the canvas — the canvas. Same node cards, same edges, same colours.

A form becomes a row, and the buyer gets an emailFilter the rows with an address, update inventory, confirm.

Support that routes itselfThe widget starts it; an AI node classifies; each category ends somewhere else.

Flow links: one run triggers the nextEach flow keeps its own canvas, its own runs and its own errors.

Mode

Deterministic, or handed to a model

Every integration node offers both. Neither is chosen for you.

Single operation

One action per event. No model involved.

Choose 1 of 16 opsFree

AI toolkit

All 16 Gmail tools, lent to an upstream AI node.

AI Toolkit16 tools per node

Sheets

Gmail

Drive

Docs

Calendar

Notion

Jira

GitHub

Shopify

Discord

Postgres

SplitMergeFilterRouterConditionalLoopAggregatorDelayLimitApprovalCacheSchema validatorCodeTransform

MCP, in both directions

Bring a server in as a credential — or publish your flows so another agent can call them.

A server, as a credential

Add the server once. Its tools show up in the AI node’s toolkit next to Gmail and Sheets, and the node still enforces the shape of what comes back.

https://mcp.linear.app/sse

Your flows, as a server

Point Claude or Cursor at your workspace and every trigger you expose becomes a tool it can call. OAuth 2.1 with dynamic client registration, so there is no key to paste.

https://api.hostwebhook.com/mcp

Chat trigger

The same conversation, from both sides

On the left, what your visitor sees. On the right, what the canvas is doing while they type.

On your site

Assistant

Gmail · Sheets · Calendar

New chat

Move my 3pm to tomorrow

update_calendar_eventsend_email

Moved to 9:30 AM tomorrow. I emailed the guests.

Type your message…

On your canvas

One AI node, holding real toolsIn toolkit mode a node lends the model every operation it has. The model chooses; the node still enforces the shape.

The widget is the trigger; the model picks which of the thirty-one tools to call. Allowed origins and the signed mode are set on the trigger, not in the snippet you paste.

While you build it

Point a real provider at localhost

A tunnel, and your debugger stays attached.

$ hostwh login
✓ signed in · token saved to ~/.hostwh/config.json

$ hostwh expose http://localhost:3000
✓ tunnel online
  https://api.hostwebhook.com/tunnel/quiet-forest-1a2b/
  → http://localhost:3000

After it ran

Every step keeps its input and its output

Not “did it fail” — what did node four receive.

Pricing

Simple, transparent pricing

Start free. Upgrade when you need more. No hidden fees, no per-seat pricing.

Free

free forever

Perfect for side projects and testing.

1,000 events / month
20 AI credits / month
3 retries / event (30 min cap)
7-day event history
Real-time dashboard
Community support

Start for free

Report an issue

Found a bug or have a feature request? Let us know — we read every submission.

Create the endpoint. Point something at it.

Start free Read the docs

Already have an account? Sign in

Receive the webhook.Then actually do something with it.