The HTTP block makes a request to an external API from inside your flow: GET to fetch data (order status, available time slots, customer details) or POST/PUT to write data back (a lead, an appointment, a note). Fields from the response become variables you use in your messages and conditions. You fill in the URL, headers, and fields — no programming needed.
What you typically connect
Any system with an API or a webhook. In practice these are the most common directions:
- Online store: order status, shipping information, stock
- CRM: create a lead, enrich a contact, look up deal status
- Calendar: fetch availability and book an appointment
- Accounting: look up invoice status or a payment link
- Make, Zapier, or n8n as a middle layer to hundreds of other tools
Safe and predictable
You only send the fields you choose yourself. Put a timeout and an error path in your flow, so a customer is never left waiting in silence when a system is briefly down.
Frequently asked questions
Do I need a developer for an API integration?
For standard systems, no: you fill in the URL, the headers, and the fields. If your system has an unusual API, a developer or our support team will get you going in half an hour.
Which methods are supported?
GET, POST, PUT, and similar requests with your own headers and JSON body, plus reading fields out of the response.
Can I connect without an API?
Yes, through Make, Zapier, or n8n. Those tools talk to hundreds of systems, and your flow only has to talk to one webhook.