The API endpoint destination lets you share a workflow connection's results securely through a private, Sheetgo-hosted URL. External tools can pull the latest data whenever they need it — a reliable, pull-based alternative to webhooks. Instead of Sheetgo pushing data out, your other systems query the endpoint on demand and always read the most recent connection result.
Why use it
An API endpoint destination gives you flexible, pull-based control over how your data is distributed. Other systems can query the latest connection results whenever they need them, keeping every integration synchronized without manual exports.
Note: The API endpoint destination is currently in beta.
What you can do
Add an API endpoint as a step in any workflow connection — on its own or alongside a standard spreadsheet destination.
Access data through a private URL that reads from a persistent cache, refreshed automatically each time the connection runs.
Generate, rename, and revoke multiple API keys to authenticate different external systems independently.
Track the endpoint status in the workflow builder, including a Never run indicator or the timestamp of the last update.
Set up an API endpoint destination
Create or edit a workflow connection and choose a source as usual.
At the destination step, under Apps & services, select API endpoint.
Sheetgo generates a private Endpoint URL. Click Copy to use it in your external system. The Status shows Never run until the connection runs for the first time, then displays the timestamp of the last update.
Under Authorization, the endpoint is protected by a Bearer API key. Click Manage keys to generate a new key or manage existing ones.
You can keep several keys to authenticate different systems independently, and rename or revoke any of them at any time.
Use the example request to pull data into your external system. Consumers fetch the cached result on demand — Sheetgo never pushes.
Click Review automation and save the connection. The cache refreshes automatically each time the connection runs.