Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Retool connector page.Get your Native Webhook URL
StackOne generates a per-connection webhook URL. You will paste it into a Retool workflow’s HTTP block so the workflow delivers events to StackOne.
- On this connection in StackOne, copy the read-only Native Webhook URL. It contains a secure per-connection token (the
?token=at the end) that identifies your account, so treat it like a secret. - The Retool HTTP block sends the full URL, including that token, so no additional authentication header is required.
Create a workflow in Retool
Events reach StackOne from a Retool workflow that makes an outbound HTTP request. Sign in to Retool and create a workflow to hold that request.
Open Workflows and click Create new
In the top navigation click Workflows, then on the Workflows home click Create new (top-right).
Choose Workflow
In the Create new menu, select Workflow (not From Template). Retool opens a new, empty workflow in the editor.
Review the workflow canvas
The editor opens with a startTrigger block (the entry point — it cannot be deleted) and a default code1 block. You will add an HTTP request block and connect it after the trigger.
Add and configure the HTTP request block
Retool has no dedicated “HTTP request” block — an outbound HTTP call is made with a Resource query block backed by a REST API resource.
Open the Blocks panel and add a Resource query
Open the Blocks panel from the left toolbar and drag a Resource query block onto the canvas, then connect it after the startTrigger block.
Set the resource, method and URL
In the block, select a REST API resource, set the method to POST, and paste your StackOne Native Webhook URL (including its ?token=) as the request URL. Click More configurations to expand URL parameters, Headers and Body. Add a header Content-Type: application/json, and set the Body to the JSON you want delivered — include an id (and optionally a type) field so downstream consumers can identify and route the event. Save the workflow and run it (or let its trigger fire); the block should return 200 from StackOne.
Available webhook events
Because the workflow’s HTTP body is fully defined by you, StackOne maps every delivery through a single generic event handler rather than a fixed provider catalog. Put an id (and optionally a type) in your JSON body so consumers can identify and route each event.
Generic Retool event
The one event type emitted for every workflow delivery.
- Retool Webhook Event (
retool.event) — emitted for every JSON body your Retool workflow POSTs to the Native Webhook URL. StackOne uses the body’sid(falling back througheventId,workflowId,appId,userId) as the event’s record id and passes your full body through as the event data.
Delivery format
StackOne emits a stable event type of retool.event for every delivery and passes your posted JSON body through untouched as the event data. The record id is taken from your body’s id field (with fallbacks), and the event date is assigned by StackOne. There is no verification handshake and no inbound signature — the ?token= in the Native Webhook URL is the security gate that identifies and authorizes your account, so keep the URL secret. If the token is missing or wrong the delivery is accepted with a 200 but the event is silently dropped.