HTTP request block
Call any external API mid-flow. Branch on the response status; extract response JSON into contact / account / agency / run variables.
Config
Request
- Method — GET / POST / PUT / PATCH / DELETE
- URL — supports
{{variable}}substitution - Query params — key/value rows
- Headers — key/value rows
- Body mode —
none/raw/json/form-encoded - Body — for raw / json modes
- Auth —
none/bearer/basic/header - Timeout — milliseconds (default 15000)
Response handling
- Auto-populated run vars — every call sets:
{{run.http_[blockId]_status}}— the HTTP status code{{run.http_[blockId]_ok}}— true when 2xx{{run.http_[blockId]_error}}— error text if any
- Extract mappings — rows that pull a JSON path from the response into a target:
- Path — JSONPath (
data.token,result.items[0].id) - Target —
run/contact/account/agency - Field — the key to write into
- Path — JSONPath (
Sockets
- On success — fires when status is 2xx
- On failure — non-2xx or network error / timeout
Use cases
- Mid-flow OTP send via an external SMS gateway
- Lookup a customer’s order status from your e-commerce backend
- Validate a coupon code against your inventory system
- Post a Slack message to your team when a flow hits a “needs human” branch
The HTTP block’s variable substitution applies to URL, query params, headers, body, and auth fields — so you can fully template a per-customer call.
Last updated on