If you want to connect different apps, APIs, and online services inside n8n, the HTTP Request node is one of the most powerful and flexible tools you’ll use.
Whether you’re pulling data, sending information to an external service, or building full automation pipelines — this node does the job.

Instead of reading dry documentation, let’s learn it through real examples + visual explanations.

Environment & Target Audience

• Platform: n8n (Cloud or Self-Hosted)
• Core Node: HTTP Request
• Recommended For:
  • Automation users
  • Developers and DevOps
  • API beginners
  • Teams building workflow automation

Example 1 — Using GET to Fetch External Data (Weather API)

A very common use case: fetching data from an external API.

Workflow Structure

Just a Start node + HTTP Request node.

Configuration

Method

GET

URL

https://api.weatherapi.com/v1/current.json

**Query Parameters**

key = your_api_key q = Tokyo

Result Output

Example JSON output:

{
  "location": "Tokyo",
  "temp_c": 13,
  "condition": "Cloudy"
}

You can now send this data to:

• Slack

• Telegram

• Email

• Databases

• Dashboards

• Internal business systems

Example 2 — Sending Data via POST (Submit JSON to Your Backend)

Another real-world scenario: posting structured data to a server.

Typical business scenarios:

• Sending order details

• Logging transactions

• Syncing data between systems

Workflow

Configuration

Method

POST

URL

https://api.example.com/order/create

Headers

Content-Type: application/json
Authorization: Bearer your_token

Body (JSON)

{
  "orderId": "A12345",
  "amount": 199,
  "currency": "USD"
}

Expected Responses

Success

{
 "status": "success",
 "message": "order created"
}

Common Failure Cases

• 401 Unauthorized

• 403 Forbidden

• 422 Validation Error

Example 3 — Webhook → HTTP Request Forwarding

(One of the Most Common Production Scenarios)

A very practical automation scenario:

“A system sends us a webhook → we forward/process/store it automatically.”

Workflow

• Webhook Node

• HTTP Request Node

• (Optional) Function / Database / Messaging Node

Webhook Settings

Mode:

Production

Method:

POST

Forwarding the Webhook Payload

In HTTP Request body:

{{$json}}

This allows automation scenarios like:

• Stripe → CRM

• Shopify → ERP

• Monitoring System → Slack

• Notion → Custom Systems

Example 4 — Importing cURL Requests (Super Useful!)

If your API provider gives cURL examples, this is a life-saver.

Steps

• 1️⃣ Open HTTP Request node
• 2️⃣ Click Import cURL
• 3️⃣ Paste:

curl -X POST "https://api.example.com" \
-H "Authorization: Bearer 123" \
-d '{ "name": "Jason" }'

n8n automatically fills:

• ✔ Method
• ✔ URL
• ✔ Headers
• ✔ Body

Massive productivity boost.

Pro Tips & Best Practices

✔ Supports Multiple Authentication Types

You can use:

• API Key

• Bearer Token

• Basic Auth

• OAuth

Just choose:

Authentication → Select Provider

✔ Retry & Timeout Protection

When APIs are unstable, configure:

• Timeout

• Retry logic

This keeps workflows safe and reliable.

✔ Combine With Other Nodes

HTTP Request works amazingly with:

• IF

• Switch

• Function

• Merge

• Databases

This is how enterprise-grade automations are built.

FAQ — Frequently Asked Questions

1️⃣ Can HTTP Request replace dedicated integration nodes?

In most cases, yes. If an API exists, HTTP Request can call it.

2️⃣ Do I need API documentation?

Yes. Either:

API docs

Postman collection

cURL example

3️⃣ Why do I get 401/403 errors?

Common reasons:

Wrong token

Wrong authentication type

Missing permissions

4️⃣ Why is the response unreadable?

Check:

Response format (JSON/XML)

Content-Type

Compression (gzip)

5️⃣ Where should I deploy n8n?

Best options:

Self-host on VPS (cost-effective & secure)

Or use n8n Cloud

Self-hosting gives full control and flexibility.