Reference · Tools
PostBin
Create temporary HTTP request collection bins, send test requests, and retrieve captured requests via PostBin (postb.in). Useful for debugging webhooks and testing HTTP integrations.
The PostBin node creates temporary HTTP request bins, sends test requests to them, and retrieves what was captured — using the free postb.in service and needing no credentials. A typical build is capturing exactly what a third-party webhook sends before you write the workflow that consumes it.
- Node type
- Action
- Parameters
- 8
- Outputs
- Output, Error
- Credentials
- None required
PostBin
Create HTTP request bins and capture requests for debugging webhooks.
Overview
PostBin (postb.in) is a free, public HTTP request catcher service. This tool allows creating temporary bins that collect incoming HTTP requests, sending test requests to those bins, and retrieving the captured request data. It supports two resources: Bin (create, get, delete) and Request (get a specific request, remove the first/oldest request, send a test request). Bins are temporary and expire automatically. No authentication is required. The Bin ID format is two 13-digit numbers separated by a dash (e.g., 1234567890123-1234567890123). The tool accepts full PostBin URLs or raw bin IDs.
Category: Data & Storage
Tool Name: postbin
Version: 1
Appearance: Icon: lucide-Inbox | Color: #6E42CE
Node Type
Action — processes input items and produces output
Input / Output
| Direction | Port(s) |
|---|---|
| Input | Input |
| Output | Output, Error |
Credentials
This tool does not require any credentials.
Resources
| Resource | Value |
|---|---|
| Bin | bin |
| Request | request |
Operations
Each resource has its own operation list. Choose the resource first, then the operation.
| Resource | Operation | Value | Description |
|---|---|---|---|
| Bin | Create | create | Create a new bin |
| Bin | Get | get | Get a bin |
| Bin | Delete | delete | Delete a bin |
| Request | Get | get | Get a specific captured request |
| Request | Remove First | removeFirst | Remove and return the first (oldest) request from a bin |
| Request | Send | send | Send a test request to the bin |
Parameters
Bin: Create takes no parameters of its own — see All Operations.
Bin: Get
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Bin ID | string | Yes | — | Unique identifier for the bin. Accepts a raw ID (e.g., 1234567890123-1234567890123) or a full PostBin URL. Supports expressions like {{ $json.binId }}. |
Bin: Delete
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Bin ID | string | Yes | — | Unique identifier for the bin. Accepts a raw ID (e.g., 1234567890123-1234567890123) or a full PostBin URL. Supports expressions like {{ $json.binId }}. |
Request: Get
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Bin ID | string | Yes | — | Unique identifier for the bin. Accepts a raw ID (e.g., 1234567890123-1234567890123) or a full PostBin URL. Supports expressions like {{ $json.binId }}. |
| Request ID | string | Yes | — | Unique identifier for the captured request. Supports expressions like {{ $json.requestId }}. |
Request: Remove First
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Bin ID | string | Yes | — | Unique identifier for the bin. Accepts a raw ID (e.g., 1234567890123-1234567890123) or a full PostBin URL. Supports expressions like {{ $json.binId }}. |
Request: Send
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Bin ID | string | Yes | — | Unique identifier for the bin. Accepts a raw ID (e.g., 1234567890123-1234567890123) or a full PostBin URL. Supports expressions like {{ $json.binId }}. |
| Bin Content | string | No | — | Content to include in the test request body. Sent as the “content” property in the JSON body. Supports expressions like {{ $json.payload }}. |
All Operations
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Max Concurrency | number | No | 10 | Maximum number of items to process concurrently. |
Output Data
Every operation produces exactly one output item per input item. The result is merged into the item JSON at the top level, so the fields below sit alongside whatever the input item already carried; anything the result does not overwrite passes through unchanged, and binary data is forwarded.
| Resource / Operation | Fields added to the output item |
|---|---|
Bin / create | binId, nowTimestamp, nowIso, expiresTimestamp, expiresIso, requestUrl, viewUrl |
Bin / get | The same set of fields as create, for the bin you asked about |
Bin / delete | success (true) and binId — the ID that was deleted |
Request / get | The captured request exactly as PostBin returns it |
Request / removeFirst | The oldest captured request exactly as PostBin returns it — the request is removed from the bin in the process |
Request / send | requestId — the ID PostBin assigned to the request that was just sent |
Field notes for the bin operations:
binId— the bin’s identifier, in{13 digits}-{13 digits}form. This is the value to feed the Bin ID parameter of later nodes.nowTimestamp/expiresTimestamp— the server’s current time and the bin’s expiry, in milliseconds.nowIso/expiresIso— the same two moments as ISO 8601 strings.requestUrl— the public URL that captures requests sent to the bin.viewUrl— the browser URL for inspecting the bin’s captured requests.
Reference the result downstream by expression, e.g. {{ $json.binId }}.
Usage Examples
- Create a new PostBin request bin
- Get details of an existing PostBin bin
- Delete a PostBin bin
- Send a test request to a PostBin bin
- Retrieve a specific captured request from a bin
- Remove and return the oldest request from a bin
Example Configuration
Create a new bin:
{
"type": "postbin",
"parameters": {
"resource": "bin",
"operation": "create"
}
}
Look up an existing bin to check when it expires:
{
"type": "postbin",
"parameters": {
"resource": "bin",
"operation": "get",
"binId": "1234567890123-1234567890123"
}
}
Delete a bin — a full PostBin URL works just as well as a raw ID:
{
"type": "postbin",
"parameters": {
"resource": "bin",
"operation": "delete",
"binId": "https://www.postb.in/1234567890123-1234567890123"
}
}
Fetch one captured request by its ID:
{
"type": "postbin",
"parameters": {
"resource": "request",
"operation": "get",
"binId": "1234567890123-1234567890123",
"requestId": "req_abcd1234"
}
}
Pop the oldest captured request off a bin:
{
"type": "postbin",
"parameters": {
"resource": "request",
"operation": "removeFirst",
"binId": "1234567890123-1234567890123"
}
}
Send a test request with a body:
{
"type": "postbin",
"parameters": {
"resource": "request",
"operation": "send",
"binId": "1234567890123-1234567890123",
"binContent": "Test webhook payload"
}
}
Send a test request with no body at all:
{
"type": "postbin",
"parameters": {
"resource": "request",
"operation": "send",
"binId": "1234567890123-1234567890123"
}
}
Chain the nodes: send a test request to the bin the previous node created, reading its ID off the item:
{
"type": "postbin",
"parameters": {
"resource": "request",
"operation": "send",
"binId": "{{ $json.binId }}",
"binContent": "{{ $json.payload }}"
}
}
Then read the request back to confirm it arrived:
{
"type": "postbin",
"parameters": {
"resource": "request",
"operation": "removeFirst",
"binId": "{{ $json.binId }}"
}
}
Error Handling
| Mode | Behavior |
|---|---|
| stop | Halts workflow on first error |
| continue | Skips failed items, passes successful ones through |
| errorPort | Routes failed items to Error output port |
Tips
Create temporary HTTP request bins, send test requests, and retrieve captured requests using the free PostBin (postb.in) service.
Frequently asked questions
Does it need credentials?
No. It uses the free public postb.in service, so there is nothing to configure or authenticate.
What is it actually for?
Seeing the real shape of an incoming request. When a provider's documentation is vague, pointing their webhook at a bin and inspecting the capture is faster than guessing.
Are the bins permanent?
No — they are temporary by design. Treat them as a debugging aid rather than anything to depend on in a production path.
Should I send sensitive data to a bin?
No. Bins are a public service, so never point a webhook carrying real credentials or personal data at one.
Build with the PostBin node
Drop it into a workflow, wire it to an agent, or call it on a schedule.
Open BusyBotLast updated . Spotted something wrong? Tell us.