WorqHat
Utility

HTTP Request

Category
Integrations
Node Type
API / External Service Connector

Overview

The HTTP Request Node allows users to send HTTP requests to external APIs or services inside a no-code workflow. It supports GET, POST, PUT, DELETE and can send/receive JSON or other formats.

It connects workflows to any web-based system for data retrieval or automation.

Description

Connect to external APIs.

The HTTP Request Node acts as a bridge between your workflow and external APIs.

Fetch Data (GET)

Retrieve info from weather, news, or DB APIs.

Send Data (POST)

Submit forms, create records, or trigger webhooks.

It can send data, retrieve data, or interact with external applications by specifying the endpoint, method, and body.

Input Parameters

Configure the API request details.

endpointUrlstringRequired
Complete API endpoint URL.
Example
"https://api.example.com/users"
methodstringRequired
HTTP Method: GET, POST, PUT, DELETE.
Example
"POST"
authTypestringOptional
Authentication: None, Basic, Bearer.
Example
"Bearer"
tokenstringOptional
Bearer token (if Auth Type is Bearer).
bodyTypestringOptional
Format: JSON, Form Data, x-www-form-urlencoded.
Example
"JSON"
jsonBodyarrayOptional
Key-value pairs for JSON body.
Example
[{ "key": "title", "value": "Hello" }]
headersarrayOptional
Custom headers (e.g., Content-Type).

Output Parameters

The node returns the API response.

statusnumberOptional
HTTP status code (e.g., 200, 404).
Example
200
responseobjectOptional
The full response body from the API.
[dynamic_fields]anyOptional
Top-level fields from the response are often exposed directly.

Output Type

Output Type: JSON Object

The node returns the parsed JSON response from the external service.

Example Usage

Example 1: POST Request

Create a new post.

{  "endpointUrl": "https://jsonplaceholder.typicode.com/posts",  "method": "POST",  "bodyType": "JSON",  "jsonBody": [    { "key": "title", "value": "hello world" },    { "key": "userId", "value": "1" }  ]}
{  "title": "hello world",  "userId": "1",  "id": 101,  "status": 201}

Example 2: GET Request

Fetch user details.

{  "endpointUrl": "https://jsonplaceholder.typicode.com/users/1",  "method": "GET"}
{  "id": 1,  "name": "Leanne Graham",  "email": "Sincere@april.biz",  "status": 200}

How to Use in a No-Code Workflow

1

Add the Node

Add the HTTP Request Node to your workflow.

2

Configure URL

Enter the Endpoint URL and select the Method.

3

Set Auth/Body

Add authentication headers or request body if needed.

4

Run & Map

Run the node to test, then map the response fields to downstream nodes.

Best Practices

  • Verify endpoint URLs before saving.
  • Use environment variables for API keys (don't hardcode).
  • Handle errors (check status code).

Do / Don’t

Do
  • ✔️ Use HTTPS for secure communication.
  • ✔️ Set timeouts or retries for critical requests.
  • ✔️ Check API documentation for correct body structure.
Don’t
  • ❌ Don’t expose sensitive tokens in public workflows.
  • ❌ Don’t ignore rate limits of the external API.

Common Errors

404 Not FoundErrorOptional
Incorrect endpoint URL.
401 UnauthorizedErrorOptional
Missing or invalid API token.
500 Server ErrorErrorOptional
External API issue; try again later.

Example Workflow Integration

Use Case: Form to API

Submit user form data to an external CRM.

  1. Form Trigger: User submits details.
  2. HTTP Request: POST data to CRM API.
  3. Return State: Confirm submission to user.

Workflow Data Flow:

{{form.email}} →  {{httpRequest.jsonBody.email}}
{{httpRequest.status}} →  {{returnState.status}}