HTTP Request

Select Method

Select the Method

Choose the HTTP method required by the target API:

• GET: Retrieve data from an API
• POST: Create a new resource or submit data
• PUT / PATCH: Update an existing resource
• DELETE: Remove a resource
• HEAD / OPTIONS: Inspect headers or verify CORS capabilities without downloading the body

Define URL

Define the URL

Enter the full URL for the API endpoint (e.g., https://api.example.com/v2/orders).

Inject values from earlier steps with {{ }}, referencing each step by the number shown on the canvas. For a field the trigger received, that gives you https://api.example.com/orders/{{ 1.order_id }}.

Use the data selector beside the field rather than typing the path. What a step exposes varies by step type, and picking the value inserts the reference that actually resolves.

Query parameters have their own section. You do not have to build a query string by hand. Add them as name/value pairs (or raw JSON) and Glow assembles the URL, handling URL encoding and nested keys (e.g., filter[status]=active or ids[]=1&ids[]=2) for you.

Authentication

Set Headers & Authentication

Authentication is its own field, above the headers. Pick the type and fill in the value. Glow builds the header for you:

Use Headers for everything else the API asks for: Accept, Content-Type, a request id. You only need to write an Authorization header by hand for a scheme none of the four types covers.

Both Headers and Query Parameters can be filled in as name/value Fields or pasted wholesale as JSON. Use whichever matches what the API’s own documentation gives you.

Payload (Body)

Configure the Payload

For methods that send data (POST, PUT, PATCH) configure the request body. Body Type offers:

Form URL Encoded and Form Data are not the same thing. If an API’s documentation shows a=1&b=2, you want Form URL Encoded.

Advanced Options

Advanced Options & Timeout

Configure behavior for slow or custom endpoints under Advanced Options:

• Timeout (seconds, 1-300): How long the step waits before aborting. Defaults to 30 seconds.
• Ignore HTTP Status Errors (4xx/5xx): Treats non-2xx error codes as successful runs, passing the error payload downstream instead of stopping the run.
• Ignore SSL Certificate Issues: Disables strict TLS/SSL certificate validation. Useful when connecting to internal staging servers, self-signed certificates, or testing environments.
• Include Full Response (status, headers, body): Returns response headers and status codes alongside the body.

JSON Response (Default)

Default JSON Output

Parsed JSON sits directly under ret:

{
  "ret": {
    "id": 1042,
    "title": "Invoice #1042",
    "status": "paid"
  }
}

Access fields directly: {{ 3.ret.id }} or {{ 3.ret.status }}.

Include Full Response

Full Response (Status & Headers)

When Include Full Response is enabled under Advanced Options, ret contains body, headers, and HTTP status codes:

{
  "ret": {
    "body": {
      "id": 1042,
      "title": "Invoice #1042"
    },
    "status": 200,
    "statusCode": 200,
    "statusMessage": "OK",
    "headers": {
      "content-type": "application/json; charset=utf-8",
      "x-ratelimit-remaining": "98"
    }
  }
}

Access fields with {{ 3.ret.body.id }} and status with {{ 3.ret.status }}.

Binary / File Downloads

Binary & Non-Text Responses

When downloading non-text files (PDFs, images, zip files), Glow encodes the binary buffer as Base64:

{
  "ret": {
    "data": "JVBERi0xLjQKJcfs...",
    "encoding": "base64",
    "contentType": "application/pdf",
    "fileName": "statement.pdf"
  }
}

This object can be handed directly to file upload steps or forwarded to external APIs.

1. Post Lead / CRM Record

Post Lead to Custom API

Send clean dynamic data from an earlier step (e.g. step 1) to an internal endpoint:

• Method: POST
• URL: https://api.yourcompany.com/v1/leads
• Auth: Bearer Token → {{ $secret.CRM_API_KEY }}
• Body (JSON):

{
  "email": "{{ 1.email }}",
  "first_name": "{{ 1.first_name }}",
  "company": "{{ 1.company_name }}",
  "source": "glow_workflow"
}

2. Loop Over Items

Call an API for Each Item in a List

When running in Run for each item mode (or inside a Repeater), reference the current item using {{ item }}:

• Method: PATCH
• URL: https://api.example.com/v2/contacts/{{ item.id }}
• Body (JSON):

{
  "status": "synchronized",
  "last_updated": "{{ $now }}"
}

Every row in the incoming list executes an isolated HTTP call.

3. Forward Full Payload

Forward Entire Webhook Payload

To forward an entire incoming event without picking individual fields, use $full_result:

• Method: POST
• URL: https://webhook.site/your-endpoint
• Body (JSON):

{
  "event_type": "typeform_submission",
  "timestamp": "{{ $now }}",
  "raw_payload": "{{ 1.$full_result }}"
}

4. Fetch OAuth Token

Fetch OAuth 2.0 Access Token

Authenticate using client_credentials with Form URL Encoded body:

• Method: POST
• URL: https://auth.provider.com/oauth/token
• Body Type: Form URL Encoded
• Fields:
  • grant_type: client_credentials
  • client_id: {{ $secret.CLIENT_ID }}
  • client_secret: {{ $secret.CLIENT_SECRET }}

The response token will be available in downstream steps as {{ 2.ret.access_token }}.