HTTP Request

Call any web API and store the response.

Method — method

Choose the HTTP method required by the endpoint. GET reads; POST/PATCH/DELETE can change data. Verify against that API's current documentation.

Input: Fixed choice.

Default: GET.

Available choices (preserve the exact value):

URL — url

Use the full public HTTPS URL. Check that it returns the resource you expect, not a login or ordinary HTML error page.

Input: Text with variable suggestions.

Format example, not a ready value for your server: https://api.example.com/data.

Default: ``.

Headers (JSON) — headers

Request headers in the editor's documented format. Use the supported secret variable mechanism for authorization; never paste a live key into an example or log.

Input: Multiline text.

Default: ``.

Body — body

Provide the payload required by the endpoint. If sending JSON, use valid JSON and the matching Content-Type. A successful transport does not guarantee application success.

Input: Text with variable suggestions.

Default: ``.

Store as — storeAs

Choose a short result prefix such as result. Later blocks must use this same prefix and run after this block. It is not a Discord channel or a persistent table.

Input: Text.

Default: response.

Read the result after this block, using its configured prefix and the fields supported by the selected operation. Do not assume every response has a text or id field.

Invoke the correct trigger with simple inputs and verify the expected effect. Confirm variables exist on this path. A preview alone does not verify Discord delivery.

Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).