Getting Started with Slashbin

Slashbin is a webhook gateway for engineers and the AI agents that work alongside them. Set up once, transform once, fan out everywhere.

The Journey

graph LR
  A["1. Create Project"] --> B["2. Receive Webhooks"]
  B --> C["3. Review DLQ"]
  C --> D["4. Build Your Model"]
  D --> E["5. Publish"]
  E --> F["6. Retry DLQ"]
  F --> G["7. Verify Deliveries"]
  style A fill:#a855f7,color:#fff
  style G fill:#22c55e,color:#fff

Your data is never lost. Webhooks that arrive before your model is ready land in the DLQ, waiting for you to tell them what to do.

1. Create a Project

Log into the console and create a new project. You'll get three things:

• Verification Key — your provider uses this to authenticate with Slashbin
• Receiver Endpoint — the URL you give your webhook provider (e.g. Shopify, Stripe)
• Destination — where Slashbin sends your transformed data

graph LR
  P["Webhook Provider"] -->|sends to| R["Receiver Endpoint"]
  R -->|verified with| V["Verification Key"]
  R -->|delivers to| D["Your Destination"]
  style R fill:#a855f7,color:#fff

Point your webhook provider at the receiver endpoint. That's it — Slashbin starts catching webhooks immediately.

2. Receive Webhooks

Trigger a few events from your provider — place a test order, update a record, push a commit. Slashbin receives and stores everything, even without a model in place.

3. Review the DLQ

Since you don't have a model yet, your webhooks land in the DLQ. This is expected — your data is safe, just waiting.

Open Operations → Dead Letter Queue in the console. You'll see your webhooks queued up and ready.

4. Build Your Model in the IDE

Open the Transformation IDE and create your Golden Model.

graph LR
  A["Raw Webhook
(500+ fields)"] -->|IDE| B["Golden Model
(only what you need)"]
  style A fill:#ef4444,color:#fff
  style B fill:#22c55e,color:#fff

The IDE gives you three panels:

• Left — the raw webhook payload from your provider
• Center — your transformation logic (JSONPath, regex, JavaScript)
• Right — live preview of your clean output

Use derived fields to compute values that don't exist in the raw data. Use filters to drop noise before it hits your systems.

5. Publish Your Model

When your output looks right, publish. Slashbin versions every model — you can roll back anytime. From this point forward, all new incoming webhooks are transformed through your model and delivered to your destination.

6. Retry the DLQ

Remember those webhooks from step 3? They're still there. Go back to Operations → Dead Letter Queue and retry them. Slashbin reprocesses each one through your published model and delivers the clean output.

This is the payoff — your data was never lost, it was just waiting for you to tell it what to do.

7. Verify Deliveries

Check the Home page for delivery results. You'll see each webhook with its status, transformed payload, and destination response.

graph TB
  subgraph "Your Slashbin Project"
    I["Inbound Webhooks"] --> T["Transformation"]
    T --> F["Filters"]
    F -->|pass| D["Delivery"]
    F -->|fail| DLQ["DLQ"]
    DLQ -->|retry| T
    D --> R["Results Dashboard"]
  end
  style I fill:#a855f7,color:#fff
  style R fill:#22c55e,color:#fff
  style DLQ fill:#f59e0b,color:#fff

What's Next?

• Recipes — Step-by-step guides for specific providers (Shopify, Stripe, and more)
• Fan-Out — Route one webhook to multiple destinations with independent filtering
• Replay — Re-deliver any webhook from the last 30 days