How to call http requests in n8n

How
to
call
http
requests

Amit Hariyale

Full Stack Web Developer, Gigawave

8 min read · April 14, 2026

You're building an n8n workflow that needs to pull data from a third-party API, but the HTTP Request node's 47 configuration options feel overwhelming. You copy a cURL command, paste it into n8n, and hit execute—only to get a 401 Unauthorized error...

This is the reality for most developers and automation engineers working with n8n. The HTTP Request node is powerful but unforgiving. Misconfigure authentication, headers, or body format and your workflow fails silently or worse, returns cryptic errors that waste hours of debugging...

Key Concepts Covered

callhttprequestsn8n

n8n HTTP Request node
REST API integration
Workflow automation
OAuth2 and API key authentication
n8n expressions and dynamic data
Error handling in n8n workflows
Response format parsing (JSON, binary, string)

Context Setup

n8n is an open-source workflow automation tool that connects services through a visual node-based interface. The HTTP Request node is its Swiss Army knife for external API communication—supporting REST, GraphQL, and raw HTTP calls.

Prerequisites: - n8n instance running (cloud or self-hosted v1.0+) - Basic understanding of HTTP methods (GET, POST, PUT, DELETE) - API endpoint URL and authentication credentials for your target service

Problem Breakdown

Webhook triggers fire but downstream systems never receive data
OAuth tokens expire mid-workflow with no refresh mechanism
Binary data (PDFs, images) corrupts during transfer due to incorrect response format handling

Solution Overview

Chosen Approach: Master the HTTP Request node through methodical configuration—starting with simple GET requests, progressing to authenticated POSTs with JSON bodies, and implementing robust error handling.

Why This Over Alternatives: - n8n's dedicated app nodes (Stripe, Slack, etc.) are limited; HTTP Request handles any REST API - Custom Code nodes add maintenance burden; HTTP Request is native and version-controlled - Webhook nodes are inbound-only; HTTP Request...

Basic Auth:** Username/password for legacy systems

snippet-1.text

filename: n8n-http-get-config.json
language: json
purpose: HTTP Request node configuration for a simple GET call with query parameters
code: {
  "nodes": [
    {
      "parameters": {
        "method": "GET",
        "url": "https://api.example.com/v1/users",
        "sendQuery": true,
        "queryParameters": {
          "parameters": [
            {
              "name": "limit",
              "value": "10"
            },
            {
              "name": "status",
              "value": "active"
            }
          ]
        },
        "options": {
          "response": {
            "response": {
              "responseFormat": "json"
            }
          }
        }
      },
      "name": "Get Users",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.1
    }
  ]
}

Header Auth:** API keys passed in custom headers

snippet-2.text

filename: n8n-http-post-auth.json
language: json
purpose: HTTP Request node configuration for authenticated POST with dynamic JSON body
code: {
  "nodes": [
    {
      "parameters": {
        "method": "POST",
        "url": "https://api.example.com/v1/orders",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "bodyParameters": {
          "parameters": [
            {
              "name": "customer_id",
              "value": "={{ $json.customerId }}"
            },
            {
              "name": "items",
              "value": "={{ JSON.stringify($json.items) }}"
            },
            {
              "name": "total",
              "value": "={{ $json.total }}"
            }
          ]
        },
        "options": {
          "bodyContentType": "json",
          "response": {
            "response": {
              "responseFormat": "json"
            }
          }
        }
      },
      "name": "Create Order",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.1
    }
  ]
}

OAuth2:** For services requiring token exchange

snippet-3.text

filename: n8n-error-handling.json
language: json
purpose: Workflow structure showing HTTP Request node with error output connected to notification
code: {
  "nodes": [
    {
      "parameters": {
        "method": "GET",
        "url": "https://api.example.com/v1/critical-data",
        "options": {
          "timeout": 10000
        }
      },
      "name": "Fetch Critical Data",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.1
    },
    {
      "parameters": {
        "subject": "API Failure Alert",
        "message": "={{ \"HTTP request failed: \" + $json.message }}",
        "toEmail": "ops@example.com"
      },
      "name": "Send Alert",
      "type": "n8n-nodes-base.emailSend"
    }
  ],
  "connections": {
    "Fetch Critical Data": {
      "main": [
        [
          {
            "node": "Process Data",
            "type": "main",
            "index": 0
          }
        ],
        [
          {
            "node": "Send Alert",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}

Additional Implementation Notes

Generic Credential Type:** For custom auth schemes
JSON:** For REST APIs ({"key": "value"})
Form-Data:** For file uploads or legacy endpoints
Raw:** For XML or custom formats

Best Practices

Store API keys and tokens in n8n Credentials, never in node parameters
Use Expression mode (={{ }}) for dynamic values, not manual concatenation
Set explicit Timeout values based on API SLAs (typically 10-30 seconds)
Enable Always Output Data in node settings to prevent workflow stoppage
Version-control workflow JSON exports for rollback capability
Hardcode secrets in URL parameters (visible in logs)
Ignore the error output branch — always handle failures
Use responseFormat: string for JSON APIs (adds manual parsing step)

Pro Tips

Batch Requests: Use n8n's Split In Batches node with HTTP Request inside to process large datasets without memory...
Credential Scoping: Create separate credentials for read-only vs. write operations; n8n's RBAC can restrict node access per credential
Response Caching: For expensive or slow APIs, insert Function node to cache responses in static data: `$getWorkflowStaticData('global').cache =...
Webhook Response Simulation: Use HTTP Request node against https://webhook.site to inspect exact headers and body your API receives
Binary Uploads: For file uploads, use bodyContentType: multipart-form-data and reference binary data from previous nodes with `={{ $binary.data...

Resources

Official Docs

Final Thoughts

The HTTP Request node is n8n's escape hatch when no dedicated integration exists. Master it and you can connect any REST API to your automation stack. The configuration complexity is the tradeoff for universal compatibility.

Next Step: Export your first working HTTP Request workflow, then modify it to call a production API you use daily. Start with read-only GET requests before implementing state-changing POST/PUT operations.

Full Generated Content (Unabridged)

Only real code appears in code blocks. Other content is rendered as normal headings, lists, and text.

Blog Identity

title: How to Call HTTP Requests in n8n
slug: how-to-call-http-requests-n8n
primary topic keyword: n8n HTTP Request node
target stack: n8n, workflow automation, REST APIs

SEO Metadata

seoTitle: How to Call HTTP Requests in n8n (Complete Guide)
metaDescription: Learn to call HTTP requests in n8n using the HTTP Request node. Master GET, POST, authentication, and error handling with practical examples.
suggestedTags: n8n, HTTP Request, workflow automation, REST API, no-code automation
suggestedReadTime: 8 min

Hero Hook

Context Setup

Prerequisites:

n8n instance running (cloud or self-hosted v1.0+)
Basic understanding of HTTP methods (GET, POST, PUT, DELETE)
API endpoint URL and authentication credentials for your target service

Problem Breakdown

Key Failure Points:

Pitfall	Symptom	Root Cause
Authentication misconfiguration	401/403 errors	Wrong auth type or credential format
Body format mismatch	400 Bad Request	Sending JSON as form-data or wrong Content-Type
Missing headers	Unexpected 200 with empty data	API requires specific headers (Accept, User-Agent)
SSL/TLS issues	Connection refused	Self-signed certs or outdated TLS versions
Rate limiting	429 Too Many Requests	No retry logic or delay between calls

Real Project Symptoms:

Webhook triggers fire but downstream systems never receive data
OAuth tokens expire mid-workflow with no refresh mechanism
Binary data (PDFs, images) corrupts during transfer due to incorrect response format handling

Solution Overview

Why This Over Alternatives:

n8n's dedicated app nodes (Stripe, Slack, etc.) are limited; HTTP Request handles any REST API
Custom Code nodes add maintenance burden; HTTP Request is native and version-controlled
Webhook nodes are inbound-only; HTTP Request enables outbound integration

Implementation Steps

Step 1: Add and Configure the HTTP Request Node

Drag the HTTP Request node onto your canvas. Double-click to open configuration.

Set Method to GET for data retrieval. Paste your API endpoint into URL. For public APIs, start with https://httpbin.org/get to verify connectivity.

Step 2: Configure Authentication

Click Authentication dropdown. Select the method matching your API:

Basic Auth: Username/password for legacy systems
Header Auth: API keys passed in custom headers
OAuth2: For services requiring token exchange
Generic Credential Type: For custom auth schemes

Create credentials via the Select Credential dropdown → Create New Credential.

Step 3: Set Headers and Query Parameters

Expand Options → Add Option → Headers. Common requirements:

Header	Value	When Needed
Content-Type	application/json	POST/PUT with JSON body
Accept	application/json	API returns multiple formats
User-Agent	n8n-workflow/1.0	APIs blocking default agents

For query parameters, use Send Query Parameters instead of hardcoding in URL.

Step 4: Configure Request Body (POST/PUT)

Set Body Content Type to match your API's expectation:

JSON: For REST APIs ({"key": "value"})
Form-Data: For file uploads or legacy endpoints
Raw: For XML or custom formats

Use n8n expressions {{ $json.fieldName }} to inject dynamic data from previous nodes.

Step 5: Handle Response and Errors

In Options, enable Response Format → JSON for automatic parsing. Set Timeout to prevent hanging requests (default 300000ms).

Add an Error Trigger node or connect the HTTP Request's second output (error branch) to handle failures gracefully.

Code Snippets

Snippet 1: Basic GET Request Configuration

code-snippet-1.text

filename: n8n-http-get-config.json
language: json
purpose: HTTP Request node configuration for a simple GET call with query parameters
code: {
  "nodes": [
    {
      "parameters": {
        "method": "GET",
        "url": "https://api.example.com/v1/users",
        "sendQuery": true,
        "queryParameters": {
          "parameters": [
            {
              "name": "limit",
              "value": "10"
            },
            {
              "name": "status",
              "value": "active"
            }
          ]
        },
        "options": {
          "response": {
            "response": {
              "responseFormat": "json"
            }
          }
        }
      },
      "name": "Get Users",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.1
    }
  ]
}

Snippet 2: POST Request with JSON Body and Bearer Token

code-snippet-2.text

filename: n8n-http-post-auth.json
language: json
purpose: HTTP Request node configuration for authenticated POST with dynamic JSON body
code: {
  "nodes": [
    {
      "parameters": {
        "method": "POST",
        "url": "https://api.example.com/v1/orders",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "bodyParameters": {
          "parameters": [
            {
              "name": "customer_id",
              "value": "={{ $json.customerId }}"
            },
            {
              "name": "items",
              "value": "={{ JSON.stringify($json.items) }}"
            },
            {
              "name": "total",
              "value": "={{ $json.total }}"
            }
          ]
        },
        "options": {
          "bodyContentType": "json",
          "response": {
            "response": {
              "responseFormat": "json"
            }
          }
        }
      },
      "name": "Create Order",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.1
    }
  ]
}

Snippet 3: Error Handling Workflow Branch

code-snippet-3.text

filename: n8n-error-handling.json
language: json
purpose: Workflow structure showing HTTP Request node with error output connected to notification
code: {
  "nodes": [
    {
      "parameters": {
        "method": "GET",
        "url": "https://api.example.com/v1/critical-data",
        "options": {
          "timeout": 10000
        }
      },
      "name": "Fetch Critical Data",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.1
    },
    {
      "parameters": {
        "subject": "API Failure Alert",
        "message": "={{ \"HTTP request failed: \" + $json.message }}",
        "toEmail": "ops@example.com"
      },
      "name": "Send Alert",
      "type": "n8n-nodes-base.emailSend"
    }
  ],
  "connections": {
    "Fetch Critical Data": {
      "main": [
        [
          {
            "node": "Process Data",
            "type": "main",
            "index": 0
          }
        ],
        [
          {
            "node": "Send Alert",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}

Code Explanation

Snippet 1 Breakdown:

"method": "GET" — Retrieves data without side effects
"sendQuery": true — Enables query parameter builder instead of URL concatenation
"responseFormat": "json" — Automatically parses JSON responses into n8n's data structure

What Can Go Wrong: Omitting responseFormat leaves binary or text responses unparsed, forcing manual JSON.parse in downstream nodes.

Snippet 2 Breakdown:

"authentication": "genericCredentialType" — Uses credential store instead of hardcoded secrets
"value": "={{ $json.customerId }}" — n8n expression injecting data from previous node's output
"bodyContentType": "json" — Sets Content-Type: application/json header automatically

What Can Go Wrong: Forgetting JSON.stringify() on array/object fields causes [object Object] to be sent literally. Always stringify nested data in expression mode.

Snippet 3 Breakdown:

"timeout": 10000 — Prevents indefinite hangs (10 seconds vs. default 5 minutes)
Error output (index 1 in connections) — Captures HTTP 4xx/5xx and network failures separately from success path

Validation Checklist

[ ] Execute node with Test Step — confirm 200 OK status in output panel
[ ] Verify response data structure matches expectations in JSON view
[ ] Check Headers tab for correct Content-Type and Authorization values
[ ] Test with invalid credentials — confirm error branch triggers appropriately
[ ] Validate expression outputs using Execute Node on preceding node first
[ ] Confirm timeout behavior by testing with intentionally slow endpoint

Expected Results:

Successful calls return parsed JSON in {{ $json }} variable
Failed calls route to error branch with message, description, and httpCode fields
Binary responses (images, PDFs) appear as binary property with mimeType metadata

Edge Cases

Scenario	Behavior	Mitigation
Empty response body	Returns {} or [] depending on responseFormat	Check status code 204 explicitly before parsing
Redirects (3xx)	Follows up to 5 redirects automatically	Disable with followRedirect: false in options if harmful
Large payloads (>10MB)	May timeout or memory-limit n8n	Stream to file using responseFormat: file
Self-signed SSL certificates	Connection fails in production	Upload CA cert or set rejectUnauthorized: false (insecure)
API rate limiting (429)	Immediate failure	Implement Split In Batches + Wait node retry pattern
OAuth token expiration	401 mid-workflow	Use n8n's built-in OAuth2 credential with auto-refresh

Best Practices

Do:

Store API keys and tokens in n8n Credentials, never in node parameters
Use Expression mode (={{ }}) for dynamic values, not manual concatenation
Set explicit Timeout values based on API SLAs (typically 10-30 seconds)
Enable Always Output Data in node settings to prevent workflow stoppage
Version-control workflow JSON exports for rollback capability

Don't:

Hardcode secrets in URL parameters (visible in logs)
Ignore the error output branch — always handle failures
Use responseFormat: string for JSON APIs (adds manual parsing step)
Chain HTTP requests without Wait nodes when hitting rate-limited APIs
Trust self-signed certificates in production environments

Pro Tips

Batch Requests: Use n8n's Split In Batches node with HTTP Request inside to process large datasets without memory issues — set batch size to match API rate limits
Credential Scoping: Create separate credentials for read-only vs. write operations; n8n's RBAC can restrict node access per credential
Response Caching: For expensive or slow APIs, insert Function node to cache responses in static data: $getWorkflowStaticData('global').cache = $json
Webhook Response Simulation: Use HTTP Request node against https://webhook.site to inspect exact headers and body your API receives
Binary Uploads: For file uploads, use bodyContentType: multipart-form-data and reference binary data from previous nodes with ={{ $binary.data }}

Resources

Official Sources:

n8n HTTP Request Node Documentation (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
n8n Credentials and Authentication (https://docs.n8n.io/credentials/)
n8n Expressions (https://docs.n8n.io/code/expressions/)
MDN Web Docs: HTTP Methods (https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods)
MDN Web Docs: HTTP Headers (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers)

High-Signal Community References:

n8n Community Forum: HTTP Request Best Practices (https://community.n8n.io/c/questions/5)
HTTP Bin Testing Service (https://httpbin.org/) — Official testing endpoint for request inspection

Final Thoughts

Preview Card Data

previewTitle: Call HTTP Requests in n8n Like a Pro
previewDescription: Master the HTTP Request node with authentication, error handling, and real-world patterns for reliable API automation.
previewDateText: Published now
previewReadTime: 8 min read
previewTags: n8n, HTTP, API, automation, workflow

Image Plan

hero image idea: Split-screen visualization showing n8n node canvas on left, HTTP Request configuration panel on right, with glowing connection line between them
inline visual 1: Screenshot of HTTP Request node authentication dropdown with credential selector highlighted
inline visual 2: Diagram showing error branch routing from HTTP Request node to Email and Slack notification nodes
inline visual 3: Side-by-side comparison of raw HTTP response vs. parsed JSON output in n8n data panel
alt text intent: "n8n HTTP Request node configuration interface showing method, URL, and authentication settings"

Key Concepts

n8n HTTP Request node
REST API integration
Workflow automation
OAuth2 and API key authentication
n8n expressions and dynamic data
Error handling in n8n workflows
Response format parsing (JSON, binary, string)

Pro TipBatch Requests: Use n8n's Split In Batches** node with HTTP Request inside to process large datasets without memory...

Next Blog

Key Concepts Covered

Context Setup

Problem Breakdown

Solution Overview

Basic Auth:** Username/password for legacy systems

Header Auth:** API keys passed in custom headers

OAuth2:** For services requiring token exchange

Additional Implementation Notes

Best Practices

Pro Tips

Resources

Final Thoughts

Full Generated Content (Unabridged)

Blog Identity

SEO Metadata

Hero Hook

Context Setup

Problem Breakdown

Solution Overview

Implementation Steps

Step 1: Add and Configure the HTTP Request Node

Step 2: Configure Authentication

Step 3: Set Headers and Query Parameters

Step 4: Configure Request Body (POST/PUT)

Step 5: Handle Response and Errors

Code Snippets

Code Explanation

Validation Checklist

Edge Cases

Best Practices

Pro Tips

Resources

Final Thoughts

Preview Card Data

Image Plan

Key Concepts

how to use Ai models in cloudflare