HTTP Request

Make HTTP requests to external APIs and services

Node Type

Action

Category

Web Integration

Icon

Globe

Overview

The HTTP Request node is an action node that makes HTTP requests to specified URLs and returns the response. This powerful integration allows you to interact with external APIs, web services, and HTTP endpoints directly from your workflows.

Key Features

  • HTTP Methods: Supports GET, POST, PUT, DELETE, and PATCH requests
  • Flexible Headers: Customizable request headers for authentication and content type
  • Request Body: Send JSON data with POST, PUT, and PATCH requests
  • Response Handling: Automatic JSON parsing with fallback to text
  • Status Tracking: Returns HTTP status codes and response headers
  • Error Handling: Graceful handling of network failures and invalid responses

Prerequisites

Network Access

Must have network access to external services

Network connectivity to target URLs
Valid and accessible target endpoints
Proper firewall and security configurations

Node Configuration

Required Fields

URL

Type:text
Required:Yes
Value Type:string

The target URL for the HTTP request. Must be a valid HTTP or HTTPS endpoint.

Method

Type:dropdown
Required:Yes
Value Type:GET, POST, PUT, DELETE, PATCH

The HTTP method to use for the request. GET for retrieving data, POST/PUT/PATCH for sending data, DELETE for removing data.

Optional Fields

Headers

Type:key_value
Required:No
Value Type:JSON

Custom headers to include with the request. Common headers include Authorization for API keys, Content-Type for data format, and custom headers required by the API.

Body

Type:JSON
Required:No
Value Type:JSON

Request body for POST, PUT, and PATCH methods. Should be valid JSON data that the API expects.

Best Practices

Do's

  • Use HTTPS URLs whenever possible for security
  • Include proper authentication headers (API keys, tokens)
  • Handle different HTTP status codes appropriately
  • Set appropriate Content-Type headers
  • Use GET for reading data, POST/PUT for writing
  • Implement retry logic for transient failures

Don'ts

  • Don't hardcode sensitive API keys (use secure storage)
  • Avoid making requests without error handling
  • Don't ignore HTTP status codes
  • Avoid sending large payloads without consideration
  • Don't forget rate limiting for repeated requests
  • Avoid using GET requests with request bodies
💡
Pro Tip: When working with REST APIs, always check the API documentation for required headers, authentication methods, and expected request formats. Use template variables to dynamically construct URLs and request bodies.

Related Resources