Automations: when this happens, do that — Trigger from anywhere: a webhook is received (2)

Conditions work too, checking payload paths with the same operators — only run when status equals paid. A post that doesn't match is logged as a Skipped run, so "why didn't it fire?" is always answerable from Run history. There is no trigger record on a webhook fire, so the steps that write into "the record" (Update the record, Generate with AI, Generate a PDF) aren't available — Create a record with {{webhook.…}} values is the usual shape: "when the payment provider posts, create a Payment record." The URL is unguessable and acts as the credential — treat it like a password, and it stays stable across edits so the system you pasted it into keeps working.