We want to setup an HTTP endpoint in UMH-core as an input. an external application will use POST request to send messages. This seems to exist as an input for redpanda connect (https://docs.redpanda.com/connect/components/inputs/http_server/) , but i wonder if i can also apply this in the config.yaml of my umh-core application? If so, is there an example of how the syntax would look like?

Yes, just use http_server! Works 1:1

Hi, how then? I tried this config yesturday dataFlow: - name: webhook-receiver benthosConfig: | input: http_server: address: 0.0.0.0:8080 path: /api/data timeout: 5s pipeline: processors: - mapping: | root.timestamp = now() root.machine = this.machine root.temperature = this.temperature output: kafka: addresses: - localhost:9092 topic: umh.v1.be.marke._raw.machine_data desiredState: active. The logging of the benthos-dataflow-webhook-receiver gave me this "2026-08-26 13:34:50.147620615 configuration file read error: /run/service/benthos-dataflow-webhook-receiver/config/benthos.yaml: (5,1) invalid type !!seq, expected object". The config for the benthos service looked like this: docker exec -it umh-core cat /run/service/benthos-dataflow-webhook-receiver/config/benthos.yaml buffer: none: {} http: address: 0.0.0.0:25877 input: [] logger: level: INFO output: [] pipeline: processors: []

Hello there! The actual "bug" seems to be your config key. You used benthosConfig as a text block, but umh-core does not recognize that key, so it silently fell back to an empty config, and Benthos then failed on the empty result. The correct key is dataFlowComponentConfig, with benthos nested inside as normal YAML, not as a text block. yaml dataFlow: - name: webhook-receiver desiredState: active dataFlowComponentConfig: benthos: input: http_server: address: 0.0.0.0:8080 path: /api/data timeout: 5s pipeline: processors: - mapping: | root.timestamp = now() root.machine = this.machine root.temperature = this.temperature output: kafka: addresses: - localhost:9092 topic: umh.v1.be.marke._raw.machine_data Try this and let us know if it deploys :).

Ok, now it deploys. Thanks!