Trigger: Signed

Fires once every document of a request is signed and the finished PDFs sit in their fields. There is no partial completion — whoever signs, signs all of them.

Step by step

1. Create an automation and pick “Signed” as the trigger.
2. As the first step, take whatever follows the signature — change stage, webhook, task.
3. The signed documents are already in their fields at this point.

Does it fire for an uploaded scan?

No. Nothing was signed — the record carries the document but no proof. To cover both routes, wait on the field, not on this trigger.

Once, or per document?

Once, when everything is signed. Per document the state would be incomplete the first time round.

What is available to the next step?

The record with its filled fields, and '{{ signature.status }}' reading “signed”.

What if only one of two documents has a target field?

Then only that one sits in a field. The other is signed and on the record, just without a field binding — the route for documents nobody should forward.