Resources · n8n integration

PostBin n8n integrationAutomate PostBin with n8n.

Stop guessing what a webhook really sends. A webhook is just a URL a service calls when something happens on its side. The PostBin n8n integration exposes 6 operations across 2 resources, from creating a throwaway bin to reading one captured request. There is no PostBin trigger, so the workflow starts elsewhere.

Try the PostBin integration on n8nSee the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the PostBin n8n integration give you?

PostBin hands you a disposable bin: a URL that accepts calls and keeps what it receives. The n8n node drives that bin from inside a workflow instead of from a browser tab. Two resources, Bin and Request, cover 6 operations: create, get and delete a bin, then get a request, remove the first one, or send a test request into the bin yourself.

The first job it does well is capture. Point a provider's callback at a bin, fire the event on their side, then read what actually arrived with request.get. You get the real body instead of the one the documentation promised, which is usually where an integration bug hides. Teams debugging a callback that feeds Slack or a database write use the bin as a neutral witness between the two systems.

The second job is replay. Send a request operation pushes a call into the bin yourself, with an optional body you control, so you can reproduce a payload shape on demand. That turns a flaky bug report into something repeatable: same content, same bin, same branch of your workflow every time. Useful when the upstream service only sends the event once a day and you need it now.

The third job is housekeeping during a test run. Remove First walks a bin one entry at a time, so a loop can process the oldest captured call and move on. Delete a bin closes the run and leaves nothing behind. A workflow that writes results into Postgres or opens an issue on GitHub can do both in the same pass.

A public template in the n8n library, workflow 2869, shows PostBin used to test webhooks in n8n without changing WEBHOOK_URL. It pairs the node with HTTP Request and a few app nodes, which is the usual shape: the bin is one step in a test loop, never the destination.

When something you need sits outside these 6 operations, the HTTP Request node calls any endpoint of the tool's API directly, and your workflow keeps its shape around it. If the whole topic is new to you, the n8n training walks through expressions and node wiring before you build a test harness on top of them.

Connect

How do you wire PostBin into a workflow?

  1. 01

    Add the node to your canvas

    The PostBin node ships with n8n, on n8n Cloud and on a self-hosted instance alike, so there is nothing to install and nothing extra to pay on the n8n side. Search for PostBin in the node panel, drop it after whatever starts your workflow, then pick Resource: Bin for the container itself, Request for the calls it collects.

  2. 02

    Generate a bin on PostBin

    Go to PostBin and follow the steps to generate a new bin. PostBin gives you a unique URL, and that URL includes a bin ID. Keep the page open while you work: the URL is what you hand to the service you are debugging, and the ID inside it is what n8n asks for. Nothing in the node replaces this step, since the bin is created on the PostBin side or through the Create a bin operation.

  3. 03

    Fill in Bin ID and choose an operation

    Pick your Operation, then enter the bin ID in Bin ID. You can type it while you experiment, or map it from an earlier node with an expression, the small piece of code in double braces that reads a field of the incoming item, for example {{ $json.field }}. Same node, same settings, whether you run it once by hand or on a schedule.

Actions

What can the PostBin node do?

The PostBin node exposes 6 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetDeleteRemove FirstSend
Bin✓✓✓
Request✓✓✓

Bin

3 operations
01

Create a bin

bin.create

What you see in n8n

Notes & use cases

Creates a bin in PostBin from inside the workflow. Handy at the top of a test run, so each execution works against its own container rather than yesterday's leftovers.

Use cases
a nightly check on a partner callback opens with this operation, then passes the bin reference down the chain with an expression such as {{ $json.field }}, so two runs never mix the traffic they captured.
02

Get a bin

bin.get

What you see in n8n

Notes & use cases

Reads back a bin you already have, so a workflow can look at the container before it touches what is inside.

Key parameters

  • Bin ID: the unique identifier for each bin, typed in while you test or pulled from a previous node with {{ $json.field }}.
Use cases
a support workflow checks the bin a colleague shared before deciding whether the debugging session is still live.
03

Delete a bin

bin.delete

What you see in n8n

Notes & use cases

Removes the bin. Run it as the closing step of a test so the throwaway container really is thrown away.

Key parameters

  • Bin ID: the unique identifier for each bin, usually the same value the rest of the branch has been using.
Use cases
a QA workflow that created a bin, captured a callback and wrote the result to a sheet finishes here, leaving no half-used bins behind for the next person.

Request

3 operations
04

Get a request

request.get

What you see in n8n

Notes & use cases

Fetches one specific request out of a bin, which is how you read what a service actually sent rather than what it claims to send.

Key parameters

  • Bin ID: the unique identifier for each bin, the container the call landed in.
  • Request ID: the unique identifier for each request, mapped from the item the earlier node produced, for example {{ $json.field }}.
Use cases
reading back a single captured call to compare its body against the mapping your workflow expects.
05

Remove First a request

request.removeFirst

What you see in n8n

Notes & use cases

Takes the first request out of the bin. Put it at the end of a loop and the bin shortens by one on every pass, which keeps a long debugging session from rereading the same entry.

Key parameters

  • Bin ID: the unique identifier for each bin, the one the loop is draining.
Use cases
a batch replay works through captured calls oldest first, dropping each one once the branch downstream has handled it.
06

Send a request

request.send

What you see in n8n

Notes & use cases

Sends a test request to the bin, so you can produce traffic on demand instead of waiting for a third party to fire an event.

Key parameters

  • Bin ID: the unique identifier for each bin, the target of the test call.
  • Bin Content: optional, and the reason this operation is worth more than a ping. Fill it to control what the bin receives; leave it alone and the call carries nothing you chose.
Use cases
reproducing an odd payload on demand while you harden the branch that parses it.
Need help

Need help automating PostBin with n8n?

A person reads every message.

FAQ

PostBin and n8n, the questions that come next

01Is the PostBin n8n integration free?
Yes, on the n8n side. The PostBin node ships with n8n, so there is nothing to install and no extra cost to add it to a workflow. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use license, and a workflow behaves the same way in both. What PostBin itself costs is a separate question and not one this page answers. Practically, the only thing that changes between Cloud and self-hosted is where the execution runs, not which of the 6 operations you get.
02What credentials or permissions does the PostBin node need?
The node has no authentication selector, so there is no credential to create in n8n before your first run. What it asks for instead is the bin ID, which comes from PostBin: you generate a new bin there and PostBin hands you a unique URL that carries the ID. Paste that identifier into the Bin ID field, or map it from an earlier node. One consequence worth planning for: anyone who has the bin ID has the same access your workflow does, so treat a bin as a scratch space and send real customer data somewhere else.
03What are the limits of the PostBin node in n8n?
The node covers 6 operations spread over two resources, Bin and Request. When what you need falls outside that list, the HTTP Request node calls any endpoint of the tool's API directly, inside the same workflow, so you rarely have to leave n8n to finish the job. The rest of the branch stays as it is: same inputs, same expressions, only the node in the middle changes. Plan for it the same way you would with any other app node, by keeping the bin ID in one place and referencing it from there.
04Does PostBin have a trigger node in n8n?
No. PostBin has no trigger node, which means a workflow around it starts somewhere else. Three options cover almost every case: a Schedule Trigger firing at a fixed interval, useful for a recurring check on captured traffic; an n8n Webhook node, a URL inside n8n that a third-party service calls, which is often what you compare the bin against; or the trigger of another tool already in the workflow. Once that first node has run, the PostBin operations sit downstream like any other action and read their bin ID from the data flowing in.
05n8n or Make for PostBin?
It depends on four things, and price is only one of them. Hosting: n8n runs self-hosted or on n8n Cloud, while Make is hosted only. Data control: a self-hosted n8n keeps captured payloads on infrastructure you own, which matters when a bin is part of a debugging loop touching production traffic. Cost model: Make bills per operation, so a loop that drains a bin one request at a time adds up differently. Visual logic: both draw the workflow on a canvas, and the feel differs enough that trying one afternoon on each beats reading comparisons.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations