🟪 HTTP Request

The HTTP Request block lets you call an external web service that offers an API, directly, without going through a ready-made integration (Airtable, Baserow, Zapier...). It handles the GET, POST, PUT, DELETE and PATCH methods (the standard ways to read, create, replace, delete or update data on the web).

It's the simplest but also the most "raw" way to connect Celestory to an outside service: a weather API, a payment service, your company's own internal server, an AI with no official integration, and so on. It needs a bit more setup than a ready-made integration, but it works with virtually any service.

📥 Inputs

• method (Choice): GET (read), POST (create), PUT (replace), DELETE (delete) or PATCH (partially update). Default value: POST.
• url (Text): The full address of the service to call (e.g. https://api.example.com/players).
• content type (Text): Specifies the format of the data being sent (e.g. application/json). Default value: application/json.
• body (Text): The content to send with the request (typically a JSON string, often produced by an Object to JSON block), used for POST, PUT and PATCH.

📤 Outputs

• result (Trigger/flow): Fires once the request has finished, so the scenario can continue.
• object (Object): The response returned by the service, already ready to use in the graph.

💡 Example

Scenario: Sending a player's final score to an internal backend

1. A game session ends with a score of 850 points, stored in a result object.
2. An Object to JSON block converts result into a JSON string.
3. An HTTP Request block is configured with the POST method, the internal backend's url, and the JSON string wired to the body input.
4. Once the request finishes, the result output triggers a confirmation message, and the object output holds the response sent back by the server.

⚙️ Technical Details

• Internal ID: http
• Difference with Voltask Webhook and Connector: This block calls an arbitrary web address directly without going through the Voltask automation engine; it's suited to simple, one-off API calls, while Voltask Webhook/Zapier/Make are better suited to more complex, multi-step automations.
• Security: Avoid exposing sensitive API keys in plain text (in the url or the request body) on a project meant to be published publicly; prefer, when possible, a call relayed through a server (e.g. via Voltask).

🔗 See also

• Connector: to merge paths in the graph, with no network call.
• Voltask Webhook: for a simple, optimized send to the Voltask ecosystem.
• Zapier / Make: to trigger a multi-step automation without configuring the HTTP call yourself.

Documented version: v1

Updated on: 06/09/2026