Skip to main content

​
Overview

The Request node lets you make HTTP API calls from your flow — send data to external systems, retrieve information, or trigger webhooks. Unlike the Tool/Function node, it gives you full control over every aspect of the HTTP request.

​
Configuration

FieldDescription
MethodGET, POST, PUT, PATCH, or DELETE
URLEndpoint URL (supports {{variable}} substitution)
Content TypeContent-Type header value
AuthorizationAuthorization header (e.g., Bearer {{api_token}})
HeadersAdditional headers as key-value pairs
Query ParametersURL query parameters
Body Modekey-value or raw (JSON/text)
Response VariableVariable name to store the response
AwaitWhether to wait for the response

​
Variable Interpolation

Every text field supports {{variable}} substitution — URLs, headers, authorization, body, everything. URL example: https://api.example.com/customers/{{customer_id}}/appointments Body example: 
{
  "name": "{{caller_name}}",
  "email": "{{caller_email}}",
  "appointment_date": "{{selected_date}}"
}

​
Response Handling

When you set a Response Variable (e.g., booking_result), three variables are created:
VariableContains
{{booking_result}}Response body (parsed JSON or text)
{{booking_result_status}}HTTP status code (200, 404, etc.)
{{booking_result_error}}Error message if request failed
Use a Logic node after the Request node to branch based on status code or errors.

​
Sync vs Async

  • Await enabled — Flow pauses until response arrives. Use when downstream nodes need the data.
  • Await disabled — Flow continues immediately. Use for fire-and-forget operations.
Request nodes have a 10-second timeout. Design your flows to handle timeouts with a Logic node checking the error variable.

Tool & Function Nodes

Pre-configured API integrations

Variables

Variable substitution reference

Logic Node

Branch on API responses

Engine & Streaming

How the engine processes requests