Receive HTTP
Description
Starts the pipeline when an HTTP request hits the pipeline's trigger URL. Exposes the request method, headers, and body stream as outputs so downstream nodes can parse the payload without buffering it into memory.
When to use
Use Receive HTTP as the entry point for pipelines that should run in response to a
webhook, API call, or any HTTP request. Each pipeline has a unique trigger URL visible
in the pipeline settings. The method output lets you validate or branch on the HTTP
verb; the headers output gives you the full multi-valued header collection (read it
with Get HTTP header or Get HTTP header values); the body stream lets you pipe the
payload directly into a parse node without loading the whole request into memory.
Pins
Output pins
| Pin | Type | Notes |
|---|---|---|
| Method | HTTP method | The HTTP verb of the incoming request (GET, POST, PUT, DELETE, PATCH, etc.). |
| Headers | HTTP headers | All request headers as a multi-valued, case-insensitive collection. Read individual values with Get HTTP header / Get HTTP header values. |
| Body | Input stream | The raw request body as an input stream. Pass to stream-to-string or a parse node; only read once. |
Execution pins
| Pin | Direction |
|---|---|
| Out | Output |
Example
Parse a JSON webhook payload and log its content. Wire the Body output of Receive HTTP
into the Input of Stream to string, then pass the Value output into the Message input
of Log message. Add Equals and Branch on the Method output to reject non-POST requests
with a Fail node before the body is read. Wire the Headers output into Get HTTP header
with Name set to X-Signature to inspect a request signature.