Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vibeflow.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

The HTTP Request Node allows you to make HTTP requests to external APIs and web services. Use it to integrate with third-party services, fetch external data, or call webhooks.

​
Required Configuration

​
URL

The endpoint URL to make the request to (supports dynamic values from previous nodes)

​
HTTP Method

Choose the request method:
  • GET: Retrieve data
  • POST: Send data
  • PUT: Update/create data
  • PATCH: Partial updates
  • DELETE: Remove data

​
Optional Configuration

​
Authentication

Support for various authentication methods:
  • None: No authentication required
  • Bearer Token: Authorization header token
  • API Key: Custom header with API key
  • Basic Auth: Username and password
  • Integration: Use credentials from a connected integration in your Connectors settings

​
Request Data

Configure what data to send:
  • URL Parameters: Path parameters in the URL
  • Query Parameters: URL query string parameters
  • Headers: Custom HTTP headers
  • Request Body (POST/PUT/PATCH only): Specify body using key-value fields or raw JSON

​
Response Handling

  • Response Path: Extract specific data from the response

​
Connections

HTTP Request nodes can:
  • Receive input from any node that produces data
  • Send output to business logic, data processing, or frontend nodes

​
Common Use Cases

External API Integration: Connect with payment processors, social media APIs, or data services Webhook Calls: Trigger external systems when events occur in your workflow Data Enrichment: Fetch additional information from external sources Third-party Services: Integrate with CRMs, email services, or analytics platforms

​
Example Workflows

  • AI Image Generation: Frontend Element → Agent Node (generate prompt) → HTTP Request (DALL-E/Midjourney API) → Return Node
  • Telegram Bot Response: Webhook Node → Agent Node (generate response) → HTTP Request (Telegram API) → Return Node

​
Authentication Examples

​
Bearer Token

Header: Authorization: Bearer your-api-token

​
API Key

Header: X-API-Key: your-api-key
(Custom header name configurable)

​
Basic Authentication

Username: your-username
Password: your-password

​
Integration

Select a connected integration from your Connectors settings. Authentication is handled automatically using the integration’s stored credentials.

Agent Node

Use AI to process HTTP request responses

If-Else Node

Handle different response scenarios conditionally