HTTP In
Creates an HTTP endpoint for flows that need to receive web requests.
Use HTTP In nodes to define the inbound paths and HTTP methods for a flow. This is the standard entry point for HTTP to Flow agents when you are building a webhook, a REST API, or simple web content.
Path parameters
HTTP In path syntax follows the Express-style route parameter syntax used by Node-RED, such as /weather-report/:reportId. In the flow, those values are available on msg.req.params.
Routing caveats
Avoid overlapping paths that depend on route order.
For example, these two routes can conflict:
/path1/subpath1/path1/*
Unlike a hand-written Express app, you should not assume the more specific route will always win. Matching can depend on the order of the entry nodes in the resulting flow JSON, and that order is not something you can reliably control.
Recommended approach
To keep HTTP flows predictable:
Prefer mutually exclusive paths whenever possible.
If you need a catch-all route, exclude the prefixes handled by your more specific routes so the wildcard never overlaps with them.
If multiple entry points should do the same work, send them into shared downstream logic with Link Call instead of duplicating the processing path.
For example, if /api, /ws, and /_old each have their own HTTP In node, a catch-all path like this excludes those prefixes:
This matches any path that does not start with /api, /ws, or /_old, stores the remainder in msg.req.params.fullpath, removes the overlap entirely, and avoids depending on route precedence.
Last updated
Was this helpful?