HTTP Requests

Make HTTP API calls to any web service.

Overview

The HTTP Requests connector is the universal escape hatch for talking to services Spojit doesn't have a dedicated connector for. It lets workflows issue any HTTP method to any URL, with arbitrary headers, query parameters, and bodies.

Reach for it when you need to integrate with an internal microservice, a niche third-party API, or a one-off webhook endpoint. For services with a dedicated Spojit connector (Shopify, Stripe, Klaviyo, etc.), prefer the dedicated connector - it handles auth refresh, pagination, and error mapping for you.

What You Can Do

The HTTP connector exposes these tools:

http-get - Issue a GET request and return the response body and status.
http-post - Issue a POST request with a JSON or form body.
http-put - Issue a PUT request for full-resource updates.
http-patch - Issue a PATCH request for partial updates.
http-delete - Issue a DELETE request.
http-head - Issue a HEAD request (headers only, no body).
http-request - The catch-all: full control over method, headers, body, and timeout.

Authentication and Setup

No connection or authentication is required to use the HTTP Requests connector itself - it is built into the platform and available in every workflow. Auth for the target API is provided per-call: pass a bearer token in the Authorization header, an API key as a query string or header, or basic-auth credentials inline.

Using in a Workflow

Add a Connector node, select HTTP Requests, and choose Direct Mode with the specific HTTP method tool. For simple GETs, use http-get. For anything involving auth headers or non-JSON bodies, http-request gives full control. Pipe the response into a Transform or Condition node to act on the result.

Tips

Store API base URLs in a Variable node at the top of the workflow so you can swap environments (sandbox vs production) without editing each step.
For paginated endpoints, wrap the call in a Loop node that increments a cursor or page parameter until the response is empty.
Always set a request timeout. Hung external services cause the entire workflow to stall and consume credits.
Capture status and key headers (X-RateLimit-Remaining, Retry-After) alongside the body for retry logic.

Common Pitfalls

Forgetting auth - Most third-party APIs return 401/403 instead of a helpful error. Check the request headers in the execution log when a call fails.
Content-Type mismatch - Sending JSON without Content-Type: application/json makes some APIs treat the body as form-encoded.
Implicit pagination - Single calls often return only the first page. Loop until the response indicates the end.
Rate limits - The HTTP connector does not auto-retry on 429. Add an explicit Condition + sleep, or use the appropriate dedicated connector if one exists.

Common Use Cases

For technical API details and field specifications, see the HTTP Requests documentation.