HTTP block reference

The full config reference for the HTTP request block. See that page for a feature overview; this page covers practical recipes.

Recipe: send an SMS via Twilio

Method: POST

URL: https://api.twilio.com/2010-04-01/Accounts/{{agency.twilio_sid}}/Messages.json

Auth: Basic, username = {{agency.twilio_sid}}, password = {{agency.twilio_token}}

Body (form-urlencoded):

• To = {{contact.phone}}
• From = {{agency.twilio_from}}
• Body = Your OTP is {{run.otp_code}}

Extract: sid → run.twilio_message_sid.

Recipe: post a Slack message to your team

Method: POST

URL: https://hooks.slack.com/services/T.../B.../...

Body (json):

{
  "text": "New lead from {{contact.first_name}} on {{contact.last_channel}}"
}

Recipe: lookup order status from your backend

Method: GET

URL: https://api.yourdomain.com/orders/{{contact.last_order_id}}

Headers:

• Authorization = Bearer {{agency.api_key}}

Extract:

• status → contact.last_order_status
• estimated_delivery → contact.last_order_eta

Then a downstream text block can render: "Your order is {{contact.last_order_status}}, ETA {{contact.last_order_eta}}."

Auth modes

• None — no auth
• Bearer — Authorization: Bearer [token]
• Basic — Authorization: Basic base64(username:password)
• Header — custom header name + value (e.g. X-API-Key)

Error handling

Every HTTP block has two output sockets:

• On success — 2xx response
• On failure — non-2xx, network error, or timeout

Wire the failure socket to either a fallback text (“Sorry, something went wrong”) or a flow_actions block that assigns to a human.