The HTTP Request node is your key to integrating with any REST API — from weather data to your own booking system. No code, no limits. This guide walks UK users through configuring the node, building integrations with common APIs, and handling real responses.
What the HTTP Request node is and when to use it • Configuring the node step by step • Authentication methods • Integration examples • Processing API responses • Pagination and batch requests • Error handling and retries • FAQ
n8n has hundreds of ready-made integration nodes: Gmail, Slack, Google Sheets, HubSpot, Stripe and more. But what if you need to connect to an API without a dedicated node? Or call your own API? That’s where the HTTP Request node comes in — a universal HTTP client that communicates with any REST API.
When HTTP Request is the right choice:
The node supports all standard HTTP methods: GET (fetching), POST (creating), PUT and PATCH (updating), DELETE (removing). It supports various body formats: JSON, form-data, binary, raw text. It sends files and receives binary responses. If it works in a browser or via curl, HTTP Request in n8n handles it too.
https://api.openweathermap.org/data/2.5/weather.q=London, appid=KEY, units=metric).{"email": "{{ $json.email }}", "name": "{{ $json.name }}"}.After a successful test, connect the HTTP Request node to downstream nodes using data from the API response.
X-Api-Key) and the key value. Store the key via Credentials for encrypted storage.Configure GET with URL https://api.openweathermap.org/data/2.5/weather and parameters q (city), appid (API key, free plan is fine), units=metric. n8n receives JSON with temperature, humidity, wind speed and weather description. Pipe to Slack or Email to send a morning weather briefing at 07:00 for UK field staff planning deliveries.
HMRC publishes monthly exchange rates as XML or JSON at trade-tariff.service.gov.uk/api/v2/exchange_rates. An n8n schedule can fetch these monthly and store them in a Google Sheet used by your finance team for VAT calculations on import/export invoicing.
Companies House offers a free API for UK business data. Register for an API key at developer.company-information.service.gov.uk, then use HTTP Request with Basic Auth (API key as username, blank password). Look up company details, directors, filing history — useful for KYC automation on new B2B customers.
Have an internal system with a REST API? HTTP Request integrates it with anything else. Example: new order in your ERP triggers a webhook → n8n pulls order details via GET to your internal API → creates invoice in Xero via POST → sends email confirmation to the customer. Zero manual steps.
APIs for Calendly, Acuity, Cal.com all speak REST. Via HTTP Request you can automatically: check availability, create bookings from form data, send Twilio SMS reminders 24 hours before the appointment, and mark completed appointments in your CRM.
Most APIs return JSON. n8n automatically parses the response — in the HTTP Request Output you see a JavaScript object, not raw text. Reference fields directly in expressions: {{ $json.temperature }}, {{ $json.user.email }}, {{ $json.orders[0].id }}.
stock > 0 && price > 100).firstName = {{ $json.first_name }}.Many APIs paginate large results (page 1, page 2...). n8n’s HTTP Request node has built-in pagination support:
For rate-limited APIs, use the Split In Batches node to process results in chunks with delays between batches — avoids hitting rate limits while preserving throughput.
APIs fail sometimes — network blips, rate limits, auth expiry, upstream outages. Handle gracefully:
n8n on UK infrastructure — connect any API
SmartXHosting n8n runs on UK data centre infrastructure with TLS 1.3, Imunify360 WAF and monitoring — reliable foundation for API-heavy workflows.
See n8n hosting plansQ: HTTP Request vs Webhook — what’s the difference?
A: Webhook receives incoming HTTP calls (you’re the server). HTTP Request makes outgoing calls to other services (you’re the client). Opposites.
Q: How do I debug a failing request?
A: Execute Node shows the raw response. Check HTTP status code first (401 = auth, 404 = URL wrong, 429 = rate-limited, 500 = upstream issue). Then check the response body for the API’s error message.
Q: Can I send files?
A: Yes. Use Body Type = Form-Data and attach binary data from a previous node (e.g. a file read from Google Drive or received in a webhook).
Q: Can I use cookies?
A: Yes — enable Cookies in the options. n8n manages the cookie jar across subsequent calls in the same workflow execution.
Q: How do I handle APIs with weird auth?
A: Generic OAuth2 or Generic Credential Type handles most cases. For truly custom auth, use Code node to compute the auth header and pass it as a custom header in HTTP Request.
Q: Are there rate limits I should worry about?
A: Yes — most APIs rate-limit. Typical limits: 100–1000 requests per minute. Use Split In Batches and add Wait nodes to respect limits. Check each API’s documentation.
Q: What HTTPS version does n8n use?
A: Modern TLS 1.2/1.3, controlled by the underlying Node.js version. SmartXHosting ships current Node.js with strong TLS.
Q: Can I see the exact bytes being sent?
A: Enable verbose logging on n8n or use a debugging service like requestbin.com as the target to inspect raw request data during development.