🌐 HTTP Request
Make REST API calls (GET, POST, PUT, DELETE, PATCH).
Overview
The HTTP Request node lets you call any REST API from your workflow. Supports all standard HTTP methods with headers, body, query parameters, and multiple authentication types.
Configuration
- Method — GET, POST, PUT, DELETE, or PATCH
- URL — the endpoint to call (supports
{{variables}}) - Headers — custom HTTP headers as JSON
- Body — request body for POST/PUT/PATCH (JSON or text)
- Query Parameters — URL query string parameters as JSON
- Authentication — select a credential (Header Auth, Bearer Token, Basic Auth, API Key, or OAuth2)
- Output Variable — name for storing the response (default:
http_response)
Response Format
The response is stored as an object with:
{{$json.http_response.status}}— HTTP status code{{$json.http_response.data}}— parsed response body{{$json.http_response.data.fieldName}}— access specific fields
Authentication Types
- Header Auth — custom header name + value (e.g., X-API-Key)
- Bearer Token — Authorization: Bearer header
- Basic Auth — username/password
- Custom API Key — generic API key in a configurable header
- OAuth2 — generic OAuth2 with token management
Common Use Cases
- CRM integration — push leads, contacts, and deals to HubSpot, Salesforce, or any CRM with a REST API
- Data enrichment — call Clearbit, ZoomInfo, or custom APIs to enrich contact records with firmographic data
- Slack and Teams alerts — post messages to channels using incoming webhook URLs when workflows complete or fail
- Payment processing — create invoices, charges, or refunds via Stripe, PayPal, or other payment APIs