Platform

When it happens here, your systems know.

Automations hook platform operations with pre, middle, and post steps; outbound webhooks deliver signed, retried events with a delivery log you can actually debug.

Explore highlights

Sound familiar?

Swivel-chair integrations

Someone copies new orders into the CRM by hand. Operations publish events. Your systems should subscribe, not poll inboxes.

The webhook you never saw

Fire-and-forget deliveries vanish into 500s. Signed, retried, and logged deliveries mean missed events get found, not lost.

Retry storms and forgery

Unsigned webhooks are spoofable; naive retries DDoS your own endpoint. HMAC signatures and idempotent, backed-off retries are the adult version.

Automation without the glue code

01Operations as triggersPick from a catalog of platform operations, like event updates, and attach what should happen around them.
02Pre, middle, post layersStructure what runs before, during, and after the operation. The middle layer carries asynchronous webhook steps.
03HTTP steps in the editorMethod, headers, and target configured in the layer editor, no middleware service to babysit.
04Signed & retriedEvery delivery is HMAC-signed with a shown-once secret, SSRF-guarded, and retried on failure.
05A real delivery logPer-endpoint history with statuses and filters. When a receiver blinks, you see it and redrive.
06The events that matterSession holds and releases, order completions. The catalog grows as the platform does.

An automation in four steps

  1. 01Pick the operationChoose what happens in the platform that should echo outward.
  2. 02Layer the stepsPre, middle, post, with HTTP calls where they belong.
  3. 03Sign the endpointCopy the one-time secret into your receiver; verification is standard HMAC.
  4. 04Watch the deliveriesStatuses in the table, retries automatic, failures visible.

Wire your first webhook

Create an endpoint in the demo and watch deliveries land.