> ## Documentation Index > Fetch the complete documentation index at: https://docs.stackone.com/llms.txt > Use this file to discover all available pages before exploring further. # Make Webhook Setup Guide > Configure Make to deliver events to StackOne. ## Prerequisites Before continuing, you should have already completed the following for this connector: Enable the connector and set up its connector profile in your project. See Managing Connectors. Make - API Token Connect an account using StackOne Hub or Auth Link. Make - API Token

Get your Native Webhook URL

StackOne generates a per-connection webhook URL. You will paste it into a Make scenario's HTTP module so the scenario delivers events to StackOne.

Create a scenario and add the HTTP module

Events reach StackOne from a Make scenario that makes an outbound HTTP request. Sign in to Make and build a scenario whose final module POSTs to the Native Webhook URL.

In Make, click + Create scenario (top-right). Add a first (trigger) module for whatever should start the scenario — a Scheduler, a Custom webhook, or any app event. For a one-off test you can skip the trigger and use Run once on the HTTP module alone.

Make new scenario canvas

Click the + to add a module and choose the HTTP app. Do NOT pick the Webhooks app — that one is for Make to *receive* incoming webhooks (a trigger URL Make listens on), not to send events out to StackOne.

Make module picker showing the HTTP and Webhooks apps

Under HTTP, select the Make a request module ("Sends an HTTP request to call any API, download a webpage, or trigger a webhook").

Make HTTP module list with the Make a request module

Configure the HTTP request

Point the module at the Native Webhook URL and send a JSON body describing the event.

In the module, set URL to the StackOne Native Webhook URL and Method to POST. Set Authentication type to No authentication (it is a required field; the `?token=` in the URL identifies the account, so no auth header is needed).

Make HTTP Make a request module fields — Authentication type, URL, Method, Headers, Body content type

Set Body content type to JSON (application/json), then in Request content enter the JSON to deliver. Include an id (used as the event's record id) and optionally a type; everything you send is passed through to StackOne as the event data. In a real scenario, map dynamic values from earlier modules rather than hardcoding — click the field and pick the upstream outputs, which Make inserts as `{{moduleId.field}}` tokens (e.g. `{"id":"{{1.id}}","type":"record.updated","data":{{1}}}`, where `{{1.id}}` is the id from the trigger module). A static example for a quick test — `{"id":"make-test-1","type":"scenario.run","data":{"hello":"world"}}`. Click Save.

Click Run once to fire it immediately, or turn the scenario On so its trigger fires it automatically. Each run POSTs the body to StackOne, which returns HTTP 200.

Available webhook events

The connector maps every scenario delivery to a single event type — the body you send in the HTTP module is what varies.

Delivery format

StackOne emits eventType `make.event`; the record id comes from the body's `id` (falling back to `eventId`/`executionId`/`scenarioId`/`hookId`, then empty), and the full JSON body you posted is passed through as the event data. Outbound delivery to your StackOne webhook endpoint is HMAC-signed (`x-stackone-signature`).

## Verify Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.