In modern automation workflows, integrating with external APIs is a must. Whether you’re pulling data from a CRM, posting to social media, or updating a database, APIs make it all possible.
n8n, a powerful workflow automation tool, offers the HTTP Request node to connect with almost any API — no extra plugins required.
In this guide, we’ll walk you through how to:
- Understand the HTTP Request node.
- Set up API calls with GET, POST, PUT, and DELETE.
- Handle authentication.
- Process API responses in your workflow.
Why Use the HTTP Request Node in n8n?
The HTTP Request node is one of the most versatile tools in n8n because:
- It supports any HTTP method.
- It can handle query parameters, headers, and request bodies.
- It works with REST, GraphQL, and other API protocols.
- It allows you to connect to APIs without pre-built n8n nodes.
Step 1: Add the HTTP Request Node
- Open your n8n workflow.
- Click “Add Node” and select HTTP Request.
- Rename it for clarity, e.g.,
Get Weather Data.
Step 2: Configure the API Endpoint
In the URL field, enter your API endpoint. Example:
https://api.openweathermap.org/data/2.5/weather
Choose the HTTP Method (GET, POST, etc.).
Add Query Parameters if needed (e.g., city, appid for API keys).
Step 3: Set Up Authentication
Most APIs require authentication. n8n supports:
- API Key (in header or query string)
- Basic Auth
- OAuth 1.0 / 2.0
- Bearer Token
Example (Bearer Token in Header):
{
"Authorization": "Bearer YOUR_ACCESS_TOKEN"
}
Step 4: Send a Test Request
Click “Execute Node” to test the API call.
If successful, you’ll see the JSON response in the output panel.
Step 5: Process API Response Data
After fetching data:
- Use the Function node to transform it.
- Store results in Google Sheets, Databases, or Cloud Storage.
- Trigger other actions in your workflow.
Example: Get Weather Data from OpenWeather API
Request:
Response Example:
{
"weather": [
{ "description": "clear sky", "icon": "01d" }
],
"main": {
"temp": 289.92,
"humidity": 56
}
}
Troubleshooting Tips
- 401 Unauthorized → Check your authentication.
- 404 Not Found → Verify API endpoint.
- 429 Too Many Requests → API rate limit reached.
- 500 Server Error → Issue on API provider’s side.
SEO Keywords for This Topic
- n8n HTTP Request node
- n8n API integration
- connect external API in n8n
- n8n automation API
- workflow automation API connection
- API authentication in n8n
Conclusion
The HTTP Request node in n8n is your gateway to limitless integrations.
By mastering it, you can connect to any API, automate repetitive tasks, and create powerful workflows without writing complex backend code.
If you want to go further, explore:
- Chaining multiple API calls.
- Error handling with IF nodes.
- Storing API data for analytics.