Use case · Five minutes to a live webhook

Private automation, on your computer.

Your workflows, your data, your machine. Share only when a webhook needs the internet, and only for as long as it does.

The steps

Five minutes to a live webhook, start to finish.

One window. The parts the agent does come back with receipts you can reopen and undo.

  1. 01 New site → n8nOne click. It starts on https://hub.test with a trusted certificate.
  2. 02 Build the flow in n8nWebhook trigger → whatever you need. Local services on the dock (a WordPress site, a database) are a hostname away.
  3. 03 Share for the webhookSharing → Go live. The public address reaches your computer through a tunnel; paste it where the callback goes.
  4. 04 Stop when doneThe link goes dark; n8n keeps running privately. Nothing was deployed anywhere.
What you end up with
✓ Automation that never leaves your machine unless you say so
✓ Webhooks that work end to end during development
✓ Logs in the app, not in a terminal
ReDock

Try it this morning.

Download ReDock, follow the steps above, and see how far you get before the coffee is cold.

Free · macOS and Windows · your sites stay on your machine