HTTP Request

Integration Node

Call any web API and use the response in your workflow

Overview

The HTTP Request node lets your workflow talk to any web service directly. Use it to fetch data from an API, send data to another system, or trigger something in a tool that doesn't have a dedicated node yet. The response is saved to a variable so later steps can read it.

When to use it

Reach for HTTP Request when you need to connect to a service that isn't in the built-in integrations. For popular apps, check the Integrations and Connect Hub nodes first — they handle sign-in for you.

Parameters

Configuration options for this node

Method

Dropdown

Required

The kind of request. GET reads data; POST, PUT, and PATCH send data; DELETE removes it.

Default: GET

URL

Text Input

Required

The web address to call. Supports variables so you can build the address from earlier steps.

Example: https://api.example.com/data

Headers

JSON (optional)

Extra request headers as JSON. Most APIs need none; use this to pass an API key when required.

Example: {"Authorization": "Bearer YOUR_API_KEY"}

Body

Text / JSON

The data to send with POST, PUT, or PATCH requests. Usually JSON.

Example: {"name": "{{ row.Name }}"}

Timeout (ms)

Number Input

How long to wait for a response before giving up.

Default: 30000

Target Variable

Text Input

The variable the response body is stored in (parsed JSON when possible, otherwise text), so later steps can use it.

Default: httpResponse

Usage Example

Fetch data from an API

Read a record and use it in the next step

Method: GET

URL:https://api.example.com/orders/123

Use a field from the response body later:{{ httpResponse.id }}

HTTP status code (from the node's output):{{ $('HTTP Request').item.json.status }}

Best Practices

Tip: Read the response with variables

After the request runs, the target variable holds the response body, so reference its fields directly, for example {{ httpResponse.name }}. Use an Apply to Each loop if the response is a list.

Error responses stop the step

A response with a non-2xx status code fails the node, so the node's error-handling and retry settings apply.

Keep API keys private

Don't hardcode secret keys where they might be shared. Store them in a variable and reference it in the Headers field.

HTTP Request

Integration Node

Call any web API and use the response in your workflow

Overview

When to use it

Parameters

Configuration options for this node

Method

Dropdown

Required

The kind of request. GET reads data; POST, PUT, and PATCH send data; DELETE removes it.

Default: GET

URL

Text Input

Required

The web address to call. Supports variables so you can build the address from earlier steps.

Example: https://api.example.com/data

Headers

JSON (optional)

Extra request headers as JSON. Most APIs need none; use this to pass an API key when required.

Example: {"Authorization": "Bearer YOUR_API_KEY"}

Body

Text / JSON

The data to send with POST, PUT, or PATCH requests. Usually JSON.

Example: {"name": "{{ row.Name }}"}

Timeout (ms)

Number Input

How long to wait for a response before giving up.

Default: 30000

Target Variable

Text Input

The variable the response body is stored in (parsed JSON when possible, otherwise text), so later steps can use it.

Default: httpResponse

Usage Example

Fetch data from an API

Read a record and use it in the next step

Method: GET

URL:https://api.example.com/orders/123

Use a field from the response body later:{{ httpResponse.id }}

HTTP status code (from the node's output):{{ $('HTTP Request').item.json.status }}

Best Practices

Tip: Read the response with variables

After the request runs, the target variable holds the response body, so reference its fields directly, for example {{ httpResponse.name }}. Use an Apply to Each loop if the response is a list.

Error responses stop the step

A response with a non-2xx status code fails the node, so the node's error-handling and retry settings apply.

Keep API keys private

Don't hardcode secret keys where they might be shared. Store them in a variable and reference it in the Headers field.

HTTP Request

Overview

When to use it

Usage Example

Best Practices

Tip: Read the response with variables

Error responses stop the step

Keep API keys private

Related Documentation

Connect Hub

Apply to Each

Set Variable

All Integrations

HTTP Request

Overview

When to use it

Usage Example

Best Practices

Tip: Read the response with variables

Error responses stop the step

Keep API keys private

Related Documentation

Connect Hub

Apply to Each

Set Variable

All Integrations