Incoming Webhook Setup
Incoming webhook setup panel with a generated endpoint URL, masked signing secret, accepted event types, and a JSON payload sample.
Incoming webhook setup panel with a generated endpoint URL, masked signing secret, accepted event types, and a JSON payload sample.
The Application Collection unlocks the source for every Application block. All Access unlocks every Collection.
Already purchased? Log in
Incoming Webhook Setup is the receive-events panel for pushing data into Acme from external systems. The generated endpoint URL, https://hooks.acme.com/inbound/ wh_8h2k4mz9r3pq, sits in a mono row with a copy icon. Below it the signing secret whsec_2f9a**** is masked with reveal and Roll secret affordances. A set of five accepted event type badges, task.created through invoice.paid, makes the contract explicit before a line of code is written. A JSON payload sample follows with a field reference table, and a tip note explains that Send test event posts a live payload so the endpoint and signature can be verified end to end.
Accepted events and field descriptions are inline arrays. The X-Acme-Signature verification reminder at the bottom is the detail that prevents teams from shipping an unsigned endpoint.
Reach for this block on the developer or integrations settings page for any product that accepts inbound webhooks, wired to your endpoint provisioning API and secret rotation endpoint.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the inbound event receiver setup for a task-management workspace. Other webhook setup panels:
Tip: showing the full payload sample with real field names removes the guesswork that causes malformed events on the first delivery.