Acquire / http · All operations

Receive incoming HTTP requests

A variant of Fetch from the web

Listen on an endpoint and turn each HTTP request that arrives into a row.

Status

In arcform

Not built yet

arcform does not do this yet. Its place on the roadmap

What other tools call it

Meridian's classification; an independent blind rating agreed on 95.7% of 324 rows (variant, version 3).

Apache NiFi (2)
  • HandleHttpRequestread 2026-09-27

    Run an HTTP server and create a FlowFile per request; pairs with HandleHttpResponse

  • ListenHTTPread 2026-09-27

    Run an HTTP server on a base path and turn incoming requests into FlowFiles

Duckle (1)
  • Webhookread 2026-09-25

    listen on a local port and collect inbound HTTP requests as rows

EasyMorph (1)
  • Incoming HTTP Requestread 2026-09-27

    Receive the HTTP request sent to a custom API endpoint hosted by EasyMorph Hub

KNIME Analytics Platform (1)
Talend (3)
  • tAPIOperationread 2026-09-27

    Handle the requests of an API operation defined in the data service contract

  • tESBProviderRequestread 2026-09-27

    Expose the Job as a web service and pass each request message to the next component

  • tRESTRequestread 2026-09-27

    Serve a REST endpoint, accepting GET, POST, PUT, PATCH and DELETE requests from clients

Background

Webhooks are user-defined Hypertext Transfer Protocol (HTTP) callbacks, usually triggered by an event such as a purchase or code being pushed to a repository.[1][2] When a webhook's event occurs, the source site makes an HTTP request to the uniform resource locator (URL) configured for the webhook.[1][3] In EasyMorph, the Incoming HTTP Request action receives a request sent to a custom endpoint on EasyMorph Hub and captures its information as a dataset.[4]

When to use it

Reach for a receiver when another system sends data as events happen rather than waiting to be asked; where the same data can be fetched on a schedule, a fetch is simpler to run. (Meridian's view) Receiving is the mirror image of calling a web service: the other system makes the request, and each request that arrives becomes a row. (Meridian's view)

An incoming webhook request should be authenticated to avoid a spoofing attack, and its timestamp verified to avoid a replay attack.[1] Ways to authenticate a webhook include HTTP basic authentication and a shared secret or digital signature sent with the webhook.[1] Check each request's signature and timestamp before its body becomes a row. (Meridian's view)

Apache NiFi's ListenHTTP processor supports only HEAD and POST requests, and answers GET, PUT, DELETE, OPTIONS and TRACE with the status code 405.[5] When Apache NiFi's ListenHTTP cannot pass on what it receives because of back pressure, it sends clients a 503 Service Unavailable response or denies connections until its output queue has space.[5]

The method

Apache NiFi's ListenHTTP processor can process incoming requests as records when its Record Reader and Record Writer properties are set.[5] Apache NiFi's HandleHttpRequest processor starts an HTTP server that listens for requests, and is designed to be paired with HandleHttpResponse to create a web service.[6] For a multipart request, Apache NiFi's HandleHttpRequest generates one output for each part, with attributes giving the part's sequence number and the total number of parts.[6]

In 2007, Jeff Lindsay coined the term webhook from the computer programming term hook.[1]

Sources

  1. [1]Webhook - Wikipediasecondary source
  2. [2]HTTP - Wikipediasecondary source
  3. [3]URL - Wikipediasecondary source
  4. [4]INCOMING HTTP REQUEST [EasyMorph Help]documentation
  5. [5]ListenHTTP - Apache NiFidocumentation
  6. [6]HandleHttpRequest - Apache NiFidocumentation