Bobbin

Bobbin is a webhook inbox and relay that runs in your own Laravel Cloud account. A webhook is an HTTP request that another service sends when something happens, such as a payment succeeding or a pull request opening. Bobbin gives each integration its own stable capture URL, stores every request sent to it exactly as it arrived, and lets you read those requests and replay any of them to a destination you choose.

It is for developers who need to see what a provider really sent, and who want to send that request on to the app that was meant to receive it without exposing a development machine to the internet.

What Bobbin does and does not do

• Each endpoint has a name and a public capture URL with a hard-to-guess identifier. Any HTTP method is accepted.
• Each capture stores the method, query string, headers, body and the time it was received.
• Each endpoint has its own retention window, from 1 to 365 days, 30 by default. A daily job deletes older captures.
• Each endpoint can redact chosen headers, and optionally the whole body, before a request is stored.
• You can replay a capture to the endpoint's one active destination. Delivery is retried and its status is shown.

Delivery is at-least-once. A destination may process a request before Bobbin records the success, so your receiver must tolerate duplicates.

Bobbin does not send one capture to several destinations, does not let you edit a captured payload before replaying it, does not verify vendor webhook signatures, and does not send webhooks to your own customers. It has no member-management screen.

How it fits with Scalpels

Scalpels installs Bobbin into your team's GitHub and Laravel Cloud accounts. It forks the repository, provisions the Postgres database, managed queue and scheduler that Bobbin declares, runs the migrations and deploys. See Install a product for how installs work in general.

Bobbin is an Experimental app in the Scalpels catalog. Installing it is available to supporters and partner teams; redeploys and upgrades of an installation you already run are free.

Bobbin is not a provider: there is no client package, and nothing needs to be attached to it. A service sends webhooks to Bobbin simply by being given a capture URL.

In these docs

• Getting started covers what the install provisions, creating the first user, and a first capture and replay.
• Capturing webhooks explains endpoints, capture URLs and what a stored capture shows.
• Replaying captures explains destinations, what a replay sends, retries and delivery history.
• Configuration lists the per-endpoint settings and the scheduled jobs.
• Use Bobbin from your agent describes the MCP tools for reading captures and queueing replays.
• Troubleshooting covers the failures you are most likely to meet.

Want a branded address for this deployment? Use your own domain.