HTTP Node

​

What Can the HTTP Node Do?

• Make API Calls: Supports a wide range of HTTP methods such as GET, POST, PUT, PATCH, or DELETE.
• Integrate Third-Party Services: Connect your workflow with platforms like CRMs, databases, AI services, or any REST-enabled API.
• Automate Data Exchange: Fetch or push data from/to external systems to power advanced automations.
• Customize Requests: Configure headers, query parameters, body payload, and timeout settings for complete control.

​

Key Features

• Flexible Method Selection: Choose the appropriate HTTP method (default: GET).
• URL Input: Specify the exact endpoint you want to interact with.
• Configurable Timeout: Define maximum wait time for responses (in milliseconds) to suit your API’s expected response durations.
• Advanced Configuration: Add headers (for authentication, content type, etc.), query string parameters, and custom request bodies—making it easy to interact with both public and private APIs.
• Dynamic Data: Use variables from previous workflow nodes as part of your URL or payload for contextual, data-driven requests.

​

Configuring the HTTP Node

• Method: Select GET, POST, PUT, PATCH, or DELETE.
• URL: Enter the API endpoint (can use dynamic variables from previous nodes).
• Timeout: Set response timeout in milliseconds.

• Easily add authentication (e.g., Bearer tokens, API keys), content-type, or any required header.

• Specify URL query string parameters as needed by the target API.

• For POST/PUT requests, define JSON or form-data payload using variables from your workflow.

• After the API call, connect subsequent nodes to process API responses (pass to an LLM, trigger a condition, etc.).

​

Example: Fetching Data from an External API

1. Input Node: Provides a city parameter.
2. HTTP Node:
   • Method: GET
   • URL: https://api.weatherapi.com/v1/current.json?key={YOUR_API_KEY}&q={INPUT/city}
   • Add necessary headers if required.
3. Next Node: Parse the temperature from the response and feed it to a Template or Output Node.

​

Use Cases

• Enrich workflow data with external information (e.g., user details, stock prices, weather).
• Send workflow outcomes to remote databases or reporting tools.
• Trigger notifications on third-party services.
• Integrate business logic into SaaS platforms.

​

Best Practices

• Handle Errors: Use Condition Nodes to handle HTTP failures (timeouts, non-200 status codes, etc.).
• Secure Credentials: Store API keys in secure environment variables whenever possible.
• Test Your API Calls: Start with small requests and check responses for proper mapping.