Webhook and HTTP: Synchronous Response Proxy Template

This template builds a request-reply proxy in Spojit: a synchronous Webhook trigger calls a downstream REST API with the http connector and returns the result to the caller through a Response node.

What It Builds

A caller sends an HTTP POST to your workflow's Webhook URL. A Connector node on the http connector uses http-post (or http-get) to call a downstream REST API with the incoming data, and a Response node returns that API's result straight back to the original caller in the same request. The result is a thin, controllable proxy between a caller and a third-party API, with Spojit sitting in the middle to reshape, authenticate, or filter the call.

The Prompt

Paste this into Miraxa, the intelligent layer across your automation, and it builds the workflow, connecting the tools for you:

Build a synchronous workflow with a Webhook trigger that takes the incoming JSON body, calls my downstream REST API at https://api.example.com/v1/lookup with an http-post on the http connector (passing my API key in the Authorization header and forwarding the request fields), and returns that API's JSON response to the caller using a Response node.

Connectors Used

  • Webhook trigger - receives the inbound HTTP POST and starts the run synchronously, verified by HMAC through a signing connection.
  • http connector - calls the downstream REST API with http-post, http-get, or http-request, forwarding fields from {{ input }}.
  • Response node - returns the downstream result to the original caller in the same request-reply cycle.

Customize It

Change the downstream URL and HTTP method in the prompt to match your API (use http-get for read-only lookups, http-put or http-patch for updates). Adjust which fields are forwarded from {{ input }}, set the right auth header for your service, and shape exactly what the Response node returns so callers get only the fields they need. Point the Webhook's signing connection at the scheme your caller uses (Spojit, Shopify, GitHub, Slack, or Custom).

Tips

  • Keep the http Connector node in Direct mode for this pattern: it is a predictable single call, so you avoid AI credits and get deterministic behavior.
  • The Response node only returns to a synchronous Webhook caller, so keep the path from trigger to response short and fast to stay within the caller's timeout.
  • Reshape the downstream payload with a Transform node before the Response node if you want to hide internal fields or rename keys for the caller.

Common Pitfalls

  • Without a Response node, a Webhook trigger simply returns 202 with an executionId and the caller never sees your downstream result, so the proxy only works when the Response node is present.
  • Forgetting to set the downstream API's auth header on the http Connector node leads to 401 errors from the third-party service, not from Spojit.
  • Long-running downstream calls can exceed the caller's HTTP timeout; for slow APIs, switch to an asynchronous pattern instead of a synchronous Response.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.