Custom Webhook Response: Send Your Own Status, Headers and Data
Reply to a webhook with data from the run: String, JSON or XML bodies, any HTTP status from 200 to 599, extra…

Part six of our FlowMattic 7.0 release series. Previously: the announcement, FlowMattic Tables, Bookings, the Builder Suite, and AI & the Browser.
Watch the API import in action — a complete custom app built straight from an API spec, no waiting for an official integration (and see Part 1 for building one by hand):
The flashy features get the headlines, but releases are won in the plumbing. 7.0 ships a set of changes squarely aimed at the people who wire FlowMattic into everything else — and a long tail of reliability work that makes every workflow steadier.
Custom Apps have always let you connect any REST API. In 7.0, you barely have to type: import actions straight from a cURL command, an OpenAPI 3.x or Swagger 2.0 spec, or a Postman 2.1 collection — paste it, upload the JSON/YAML, or fetch it from a URL.
FlowMattic discovers the actions, shows you a preview, and builds the app — either a new one or appended into an existing app with sensible skip/duplicate handling. Body, query, path and header fields are auto-filled from the spec. A vendor’s entire API surface becomes a FlowMattic app in the time it takes to find their docs page.
Webhook triggers gain an optional custom slug: instead of a numeric workflow ID, your endpoint can be /webhook/capture/orders-api — human-readable, and stable even if you recreate the workflow. The auto-generated URL keeps working in parallel, so nothing breaks while you migrate senders over.
response_headers key, ready for the next stepA release this size comes with receipts. Among the fixes shipping in 7.0:
FlowMattic 7.0 is a free update for license holders — one click from your dashboard, and integration updates never touch your workflows, connects or task history. And we’re not done: the next post covers the feature that changes how workflows get built in the first place.
Next in the series: Jaadu — describe the change, watch it build.
Reply to a webhook with data from the run: String, JSON or XML bodies, any HTTP status from 200 to 599, extra…
Post workflow data to any webhook URL as JSON, multipart form data or URL-encoded fields, with nested bracket keys and the receiver's…
Give any app a URL on your WordPress site and turn each request into a workflow run, with signature checks, sample payloads…