Overview
This lesson is part of the n8n AI Automation - Zero to Hero course, Section: 3. Deep Dive Concepts.
Watch the video above for the full tutorial, or read the written guide below.
What is the HTTP Request node in n8n?
The HTTP Request node is n8n's built-in API client, comparable to Postman, that lets you make GET, POST, PUT, and DELETE requests to any external service with a REST API. It's the correct tool when no dedicated n8n integration exists for the app you want to connect. You configure a method, URL, authentication, query parameters, headers, and an optional request body, then the node returns the response data for downstream use in your workflow.
How do you configure the HTTP Request node in n8n?
The HTTP Request node offers two configuration paths. The first is parameter-by-parameter: set the Method (GET to fetch data, POST to create, PUT to update, DELETE to remove), paste the API's endpoint URL, choose an authentication type, and add any query parameters or headers the API requires. For the AccuWeather one-day forecast API, that means selecting GET, pasting the location-specific endpoint URL, leaving authentication as None, turning on query parameters, and adding the apikey field with your key. The node executes and returns the forecast response (minimum and maximum temperature, conditions) for the requested location.
Authentication splits into two buckets. Predefined credential types cover popular services n8n already supports, including Airtable and Slack, so you pick the service name and supply your credentials. Generic credential types handle everything else: Basic (username and password), Bearer Token, and OAuth2. When an API authenticates via an API key sent as a query parameter, like AccuWeather, you select None in the authentication field and pass the key in the query parameters section instead, bypassing the credential system entirely.
The second path is Import cURL. Most API documentation pages include a sample cURL command you can copy directly. Paste it into the Import cURL dialog and the node auto-fills the method, URL, query parameters, and headers in one step. The AccuWeather cURL sample produces the same New York forecast result as the manual setup, confirming both paths are equivalent. For complex requests with many parameters or headers, cURL import eliminates the bulk of manual entry. Query parameters and URL segments can also be set dynamically using n8n expressions, letting earlier nodes in your workflow drive the API call.
Key Takeaways
- The HTTP Request node acts as a Postman-style REST API client inside n8n, covering any service that lacks a dedicated built-in node.
- GET fetches data, POST sends new data, PUT updates a record, and DELETE removes one. For soft deletes (flagging a record rather than permanently removing it), PUT is the correct method because you're updating, not deleting.
- Predefined credential types handle popular services n8n already knows (Airtable, Slack, and others). Generic types cover Basic, Bearer Token, and OAuth2 for everything else. API-key-in-query-parameter services like AccuWeather need no credential record at all.
- The cURL Import option auto-configures the node from a copied cURL command, saving significant setup time for requests with many headers and parameters.
- Query parameters can be set dynamically with n8n expressions, so values from earlier nodes can populate API call fields at runtime.
Related Lessons
- Lesson 11: How Branching works in n8n Workflows | Smart Automations with Multiple Paths
- Lesson 12: How to Use Merge Node in n8n | Combine Data Like a Pro
- Lesson 13: How to Use Set Node in n8n | Edit Fields Node | Add, Edit, Clean Data
- Lesson 14: How to Use Aggregate Node in n8n | Combine & Summarize Data
- Lesson 15: How to Use Remove Duplicates Node in n8n | Clean Your Data Fast
Next Steps
Continue your n8n journey with the full n8n AI Automation - Zero to Hero course.
