Prepare signature (Youtrust)
Creates a draft Youtrust request, uploads its documents with Smart Anchor analysis, and prepares its signatories without starting the signing lifecycle yet.
Vue d’ensemble
Prepare signature (Youtrust) separates preparation from activation. Use it when the process must retain the request as draft before sending it or when it explicitly composes the Youtrust steps.
The node uploads PDF or DOCX files, asks Youtrust to interpret their Smart Anchors, and adds signatories in supplied order.
- The request remains in draft.
- Documents with no detected anchor are rejected.
- The output can be bound to
Send for signature (Youtrust).
Typical scenario
A process prepares a contract and its signatories, performs a final business validation, then activates the request in a separate step.
Quick start
Bind the documents and contacts, then choose the channel that will be used at activation time.
Minimum preparation
- Active Youtrust configuration
- PDF or DOCX with Smart Anchors
- Contacts consistent with
s1,s2, etc.
Next step
- Bind
signature_requesttoSend for signature (Youtrust) - Keep document and signatory outputs for tracking
| Parameter | Binding | Role |
|---|---|---|
documents | documents_to_sign | Fichiers signables |
signers | signing_contacts | Ordered contacts |
Process example
Prepare documents and signatories before controlled activation in a separate step.
Data resolution
The node builds the request from linked Ormuz objects.
| Data | Source or rule |
|---|---|
| Champs | Smart Anchors contained in each document. |
| Informations signataires | Ormuz contacts supplied in signers. |
| Canal futur | delivery_mode, with email as default. |
| Ordre | Signatory list when ordered_signers is enabled. |
Parameters 10
Request and documents
Configuration, name, and documents defining the request.
Signatories and security
Recipients, order, signature level, and authentication.
email lets Youtrust send invitations; embedded prepares delivery of the link in an embedded experience. This advanced setting does not itself trigger signing.s1, s2, etc. indexes used by Smart Anchors.simple by default or advanced. Verify that your account and selected authentication mode support the requested level.no_otp, email_otp, or sms_otp. SMS mode requires a usable phone number to be available to Youtrust.Lifecycle and retention
Deadline, business reference, and proof retention.
expired route.Outputs 3
Youtrust request
Request, documents, and people tracked at Youtrust.
Behavior
Create the draft
A signature request is created with its name, channel, order, and optional deadline.
Upload the documents
Files are sent with Smart Anchor analysis enabled.
Check the anchors
Preparation fails when Youtrust detects no anchor in the signable documents.
Add signatories
Contacts become signatories associated with the requested level and authentication.
Expose the draft
The prepared request, documents, and signatories become available to following steps.
Limits and responsibilities
- The node does not activate the request.
- It does not retrieve signed documents or audit trails.
- The process remains responsible for connecting the prepared request to activation or another compatible operation.
Troubleshooting
Preparation rejected
Check file format, size, and presence of at least one valid Smart Anchor.
Wrong signatory on a field
Align s1, s2, etc. indexes with the exact order of signers.
Request already active
A request that has left draft cannot be prepared as a new request; continue its current lifecycle.
Smart Anchors Youtrust
Smart Anchors are text markers placed directly in the PDF or DOCX. Youtrust creates each signature field at the marker's location.
{{s1|signature|85|37}} creates an 85 × 37 px signature field for the first signatory.| Segment | Signification |
|---|---|
s1 | First contact in signers. Use s2, s3, etc. for following signatories. |
signature | Field type created by Youtrust. |
85 | Field width in pixels. |
37 | Field height in pixels. |
- Write each anchor on one line and keep all its segments in the same text block.
- Prefer Arial between 10 and 14 px; set the text color to the background color so it remains invisible in the final document.
- Every signatory index must exist in the request. An
s2anchor creates no field when only one signatory is supplied. - The node automatically enables anchor analysis and rejects preparation when no anchor is detected in signable documents.
See the Youtrust Smart Anchors documentation for other field types and advanced variants.