How it works
Why webhooks
They reduce unnecessary requests and react faster to important statuses.
n8n recipe
React to completed or failed Yadulink jobs from n8n.
This recipe replaces constant polling with a webhook trigger that listens to job status changes.
What the workflow covers
Nodes and logic
This page describes the recipe publicly; importable JSON files remain protected by API access.
Events
Listen only to useful events.
`job.completed`, `job.failed`, `job.canceled`.
Security
Enable signature verification.
Reject unverified payloads.
Routing
Send each status to the right action.
CRM note, Slack alert, retry, or exclusion.
Verified facts
What the tool should clarify before being used.
Use caseBased on the internal `yadulink-job-webhook-trigger.workflow.json` example.
Expected outputYadulink trigger for job events.
Method proof`job.completed`, `job.failed`, `job.canceled`.
Verification method
How to turn the template into an actionable step.
- 01 Events `job.completed`, `job.failed`, `job.canceled`.
- 02 Security Reject unverified payloads.
- 03 Routing CRM note, Slack alert, retry, or exclusion.
How it works
Handle failures
A failed job should trigger explicit action: retry, data correction, or alert.
