Output · Send and serve

HTTP Endpoint

Publishes the table as JSON at a local web address on your machine, so other tools can fetch it. Each run refreshes what the address returns.

Also known as: Local API, serve

How it works

Wire a table in and run the node. It writes a snapshot of the table under the project's endpoints/ folder and the desktop app starts a small local server for it; the Endpoint URL field then shows an address of the form http://127.0.0.1:<port>/endpoint/<node id>, with buttons to copy it or open it in your browser. A GET request on that URL returns JSON with the shape { "columns": [...], "rowCount": N, "rows": [ {...} ] }. Every run re-publishes the latest data; the server only answers on your own machine and stops when the project is closed or the app quits, so the node runs again on the next Run to bring it back. There is nothing else to configure.

Inputs and outputs

Settings

Example

A spreadsheet macro or a local dashboard needs the current stock levels. Wire the stock table into the node, run it, copy the Endpoint URL from the panel and point the other tool at it; after each pipeline run the same URL returns the fresh rows.

More in Send and serve

• Email — Sends an email through a saved mail connection, with the table in the body or attached as a CSV. It can use a report as the email body.
• Slack — Posts a message to a Slack channel when the workflow runs. The message can include the first rows of the table, such as a daily KPI alert.
• HTTP Request — Sends the data to a web address with POST, PUT or PATCH, as JSON, form fields or a file. For example, push results to a webhook.