Mode d'emploi
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.
Extraits citables
Ce que l'outil doit clarifier avant d'être utilisé.
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`.
Méthode de vérification
Comment transformer le template en action exploitable.
- 01 Events `job.completed`, `job.failed`, `job.canceled`.
- 02 Security Reject unverified payloads.
- 03 Routing CRM note, Slack alert, retry, or exclusion.
Mode d'emploi
Handle failures
A failed job should trigger explicit action: retry, data correction, or alert.
Maillage interne