HTTP API

Send a request to any API for each row, see what comes back, and add the fields you need as columns.

Before you begin

Have these ready:

• The API documentation, endpoint, method, login details, and fields you need to send.
• A test row in Data.
• Any shared secrets saved as environment variables.

Choose how to set it up

Option A: Generate the request

Use Generate when you want Floqer to set up the request for you.

• Describe what the request should do in What should this API call do?
• Add a public Documentation URL (optional) if you have one.
• Click Generate, then check the completed request in Configure.

Generate replaces anything already entered in the drawer. It leaves details blank when it cannot work them out. Nothing is saved or run until you choose to.

The prompt is required. If Floqer cannot read the documentation URL, it builds the request from your description alone.

Option B: Configure it yourself

Type / in any request input to add a variable from the current row or an earlier action. For Method, switch the dropdown to a text field first.

• Method. Choose GET, POST, PATCH, PUT, DELETE, HEAD, or OPTIONS. A method supplied by a variable can use upper or lower case and can have spaces around it, but it must match one of these options.
• Endpoint. Enter the full http:// or https:// URL without the method. Variables can fill part or all of the URL. A blank or invalid URL fails the cell. If the URL already has query parameters, Floqer keeps them and adds the ones entered below.
• Query parameters. Add each parameter as a name and value. Floqer ignores blank names, keeps repeated names, and encodes the values for the URL. Numbers and booleans are sent as text. Objects and arrays are sent as JSON text. A null or missing value is sent empty.
• Headers. Add each header as a name and value. Floqer ignores blank names, removes spaces around names and values, and replaces line breaks with spaces. Numbers and booleans are sent as text. Objects and arrays are sent as JSON text. When a request has a body and no Content-Type, Floqer adds Content-Type: application/json.

Body has two options:

• Key-value builds a simple JSON object. Skip if empty leaves out null, missing, empty, or space-only values, while keeping 0 and false. If the same key appears more than once, Floqer uses the last value.
• JSON accepts a complete JSON object, array, number, boolean, string, or null. It must be valid JSON. Keep variables inside quotes in the editor.

A blank body, {}, [], or null sends no body. GET and HEAD never send one. The other methods can, including OPTIONS.

• Timeout. Open Advanced to choose how long Floqer waits for the complete response. The default is 60 seconds. You can enter 1 to 300 seconds, and Floqer rounds it to a whole number. Clearing the field resets it to 60.
• Run condition. Add rules when the request should run only on certain rows. Other rows are skipped.

Save and test the request

Click Save & run first cell to save the action and run it on the first row in Data. If automatic publishing is off, Floqer publishes the workflow first. Only that cell runs. The drawer stays open, shows that Floqer is waiting, then displays the result.

• An invalid method, URL, or JSON body blocks the save and run.
• If there are no rows, Floqer saves the action and asks you to add one.
• Workflow templates show only Save because they have no Data row.

The same button also has Save & run 10 rows and Save & run all rows. These close the drawer after the run starts.

The first row appears under First cell result in Columns from response. Running other rows does not replace it. Rerun row 1 when you want a new sample.

Read the result

Every result has two sections:

• Response contains the complete body returned by the API.
• Metadata shows the status code, whether the body is JSON, how long the request took, and the body size. The field names are status, isJson, durationMs, sizeBytes, and attempts.

Floqer reads valid JSON even when the API labels it incorrectly. If the body is a JSON string that contains valid JSON, Floqer reads that too. Other bodies stay as text.

• A 204 response has an empty Response, isJson is false, and sizeBytes is 0.
• A response containing only a string, number, boolean, or null has no fields to open.
• Objects and arrays show 100 entries at a time. Click Show … more to keep reading.

+ Add Column appears beside fields under Response. Clicking it creates a separate Formula action and column for that field. It does not change the HTTP API action. Metadata fields do not have this button.

Retry failed requests

Retries are off by default. Turn on Retry on failure in the Advanced section of the drawer and choose exactly which status codes retry. The switch alone retries nothing.

• Max retries is the number of extra attempts after the first request, 0 to 5. The default is 2.
• Retry status codes starts empty. Type a 3-digit code such as 429 or 503 and press Enter. Only the codes in this list retry.
• Timeouts and connection errors are not retried.
• Floqer will not save the switch on while the list is empty. The drawer says "Add at least one status code to retry".
• A retry sends the request again. On a POST, PUT, PATCH, or DELETE that can create or change the same record twice, so turn retries on only for calls the API can safely receive more than once.

How retries run:

• Retries happen inside the action before the row completes. Each row costs one credit, produces one result, and nothing downstream runs until the final attempt.
• The wait between attempts grows from 0.5 to 10 seconds. A Retry-After header is honored up to 30 seconds. If the header asks for longer, Floqer saves that response instead of waiting. The whole call stops after 5 minutes.
• The Timeout field applies to each attempt, not the whole call.
• When retries run out, the final status is saved in Response and Metadata as usual.
• Metadata includes attempts, the number of requests made for that row. It is 1 unless retries ran. durationMs covers every attempt.
• The same settings are available through the public API in Configure Action as retry_on_failure, max_retries, and retry_status_codes.

There is no requests-per-second setting. Start with Save & run first cell before running every row, and use Save & run 10 rows for a larger test. If an API returns 429 and you have not added it to Retry status codes, the row still finishes: read the message in Response, follow the waiting time the API gives, then rerun the affected cells.

Troubleshooting and limits

• The API returns an error status. A 4xx or 5xx response still completes the row. The returned body is in Response and the status is in Metadata. For 401 or 403, check the endpoint, credentials, and headers.
• Floqer cannot reach the API. An invalid URL, DNS or TLS error, refused connection, broken redirect, or timeout fails the cell. Retries do not cover these. If it happens on a retry attempt, the error ends with (after N attempts).
• The API redirects the request. Floqer follows up to five redirects and forwards every header, including Authorization. A 303, or a 301 or 302 after any method other than GET or HEAD, changes the next request to GET and removes the body. A 307 or 308 keeps the method and body. A loop or sixth redirect fails.
• The response is large. Up to 10 KB stays in the cell. A response over 10 KB and up to 25 MB is stored separately and loaded when needed. Anything over 25 MB fails.
• The API expects another body format. HTTP API sends JSON only. It does not send form data, multipart bodies, or file uploads. It reads JSON and text responses, not binary downloads.
• The API returns more than one page. One request returns one page. Floqer does not follow a cursor or fetch later pages automatically.
• You need response headers. Response headers are not saved as outputs. Metadata contains only the status, JSON check, duration, size, and attempt count.
• You open an older HTTP API action. It keeps its previous error behavior until you save it with the new Response output. Opening the drawer alone does not change how it runs.