Input

API webhook

POST signed payload

API webhook is the older, signed-payload trigger that lets another piece of software start a job by sending dojobase a secure message. When a system you run reaches a certain moment, it pings this node and your workflow runs, no person involved.

How it works

A webhook is just a way for one program to poke another and say "something happened, here is the detail." This node is the poke-able address for your workflow. Your other system posts a message to it, and that message becomes a new job.

The signed part means each message carries a secret stamp that proves it really came from you, so strangers cannot fire your workflow. This is the trusted, machine-to-machine door, meant for developers wiring two products together rather than for a person clicking a button.

This is the legacy version of the trigger; there is also a newer, more flexible Webhook node. Keep using this one if it is already connected to a system that speaks to it, and reach for the newer node when you are setting up something fresh.

Common use cases

Real situations where this node earns its place in a flow.

Accept a signed payload

For a system already wired to send a signed POST, this starts a job straight from that JSON.

Trigger from your backend

Have your own server fire a job when a record is created or a status changes.

API webhook in a workflow

A simple example of where this node sits in a flow.

API webhook POST signed payload Classify Select Case · branch per rule Analyze Underwriting pass Webhook POST report JSON

What you set up

  • Copy the node's address into the system that will call it.
  • Share the signing secret so that system can stamp its messages.
  • Decide what pieces of the incoming message your workflow should read.

Common questions

Do I need a developer to set this up?

Usually yes, since another system has to be configured to send the signed message. For simpler cases a person can start a job with the upload form instead.

Should I use this or the newer Webhook node?

For a brand new integration, prefer the newer Webhook node. Keep this one if it is already wired to a working system.