What it does
Webhooks and HTTP requests connect FlowWP to systems that have no dedicated integration. A webhook lets an outside service start a workflow on your site; an HTTP request lets a workflow call any API.
Receiving webhooks
The A webhook is received trigger gives a workflow its own address. When another system posts to it, the payload becomes trigger data that later steps can use as tokens. Two webhooks arriving at the same moment cannot both start the same run twice: deduplication is enforced by a unique index, not a check that races.
With Respond to webhook, a workflow can also send a reply back to the caller.
Sending HTTP requests
The HTTP Request action sets the method, URL, headers, query parameters and body, and makes the response available to the next step. Values from earlier steps can go anywhere in the request.
Security by default
Every request URL is checked immediately before it is sent — not only when the workflow is saved — because the URL is often a token whose value comes from outside. FlowWP resolves the host and blocks private, loopback and link-local addresses, including cloud metadata endpoints, which protects your server from being used to reach its own network. A specific internal host can be allowed deliberately, one host at a time.
Details
Every plan, Free included, has unlimited webhooks and HTTP requests. Responding to webhooks is on Business and above. The HTTP request sends data only to the address you give it.
