Spojit
Webhooks

A signed URL that
runs your workflow

Give any workflow its own webhook URL. Software that can make an HTTP request can start a run and get an execution id back. Payloads are signed and verified, and transient failures retry on their own.

POST/hooks/9f2a1c7e
X-Signature: sha256=4c1f...
{ "event": "order.created", "id": "1042" }
verify
202 Accepted
executionexec_5f17c2
workflowOrder sync
How it works

From HTTP request to running workflow

01

Generate the URL

One click gives the workflow a unique, unguessable webhook endpoint with a signing secret.

02

Point your app at it

Paste the URL into any system that fires webhooks. Spojit verifies the signature on every request.

03

The workflow runs

A valid request starts a run immediately and returns an execution id you can track.

Capabilities

Built for production

Signed and verified

Every payload is checked against a signing secret, so only requests you trust can start a run.

Push delivery

Runs start the moment a request arrives. No polling interval and no waiting for the next check.

Execution id back

The response returns an id for the run it started, so the caller can follow what happened.

Automatic retries

Transient failures downstream are retried with backoff, so a brief blip does not lose the event.

Any JSON payload

Send the structured body your app already produces. It flows straight into the workflow as input.

Rotatable URLs

Leaked an endpoint further than you meant to? Rotate it, and the old URL stops working at once.

Use cases

Wherever software calls software

App events

A new order in Shopify, a merged pull request, a Stripe payment. Turn each event into a run.

CI/CD and ops

Kick off a workflow from a pipeline, a deploy hook, or an alerting tool that can POST.

Third-party callbacks

Receive the callbacks vendors send when something finishes, and act on them automatically.

Internal services

Let your own systems start workflows with a single authenticated HTTP request.

The difference

Webhook or mailhook

Same idea, different transport. Both give a workflow an address the outside world can hit.

Pick a webhook when

  • The sender is software that can make an HTTP request
  • You want signed, verified payloads and an execution id back
  • The payload is structured JSON from an app

Pick a mailhook when

  • The sender can only send email
  • You want zero setup beyond typing an address
  • The payload is a message, like an invoice or a report

Give your workflow a URL

Start free, generate a webhook, and trigger your first run with an HTTP request. No card needed.