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.
{ "event": "order.created", "id": "1042" }exec_5f17c2From HTTP request to running workflow
Generate the URL
One click gives the workflow a unique, unguessable webhook endpoint with a signing secret.
Point your app at it
Paste the URL into any system that fires webhooks. Spojit verifies the signature on every request.
The workflow runs
A valid request starts a run immediately and returns an execution id you can track.
Built for production
Signed and verified
Every payload is checked against a signing secret before anything runs. GitHub, Shopify, Slack and Svix are handled natively, with a custom HMAC option for anything else.
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.
Rotate the signing secret
Add a new secret, move the sender across, then delete the old one, so rotation costs you no downtime. A leaked URL is little use on its own, because an unsigned payload never starts a run.
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.
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
Toda execução, com as mesmas garantias
Give your workflow a URL
Start free, generate a webhook, and trigger your first run with an HTTP request. No card needed.