Output

Webhook

POST report JSON

Sends the job's result to another piece of software by posting it as JSON to a URL that system gave you, so your other tool updates on its own.

How it works

A webhook is how two systems talk without a human in between. When the job reaches this node, dojobase packages the result as structured data (JSON) and posts it to a web address (a URL) that your other software published for receiving updates. That system then does whatever it does with the data: create a record, move a deal, kick off its own process.

This is the node to reach for when you want the result to land inside your CRM, database, accounting tool, or a custom app rather than in someone's inbox. If your other software or your developer says 'give me a webhook URL,' this is the matching sender.

You control exactly what gets sent and can add a secret header so the receiving system can confirm the request truly came from you and not an impostor.

Common use cases

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

Push results to a system

POST a job's data to your CRM, ERP, or database when it completes.

Send to Zapier or Make

Fire the result into an automation platform to fan it out further.

Kick off the next process

Notify another service that a job is done so it can pick up from there.

Webhook in a workflow

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

Extract PDFs → structured data Analyze Underwriting pass Webhook POST report JSON

What you set up

  • Paste the destination URL that the receiving system gave you.
  • Choose or shape the JSON payload of job values to send (for example the result, a status, and a reference).
  • Optionally add an authentication header or secret so the receiver can verify the request is genuinely from dojobase.

Common questions

What is a webhook in plain terms?

A one-way message from dojobase to another app's listening address. When the job finishes, dojobase posts the data to that address and the app reacts automatically, no login or copy-paste needed.

How does the receiving system know it's really us?

You can add a secret header or signing value. The receiver checks it on every request and rejects anything that doesn't match, so it won't act on forged data.