YoutrustRouteurStableSend document for email signature (Youtrust)
Creates a Youtrust request from documents containing Smart Anchors, invites one or more signatories by email, and routes the process according to the final result.
Vue d’ensemble
Have a document signed by email (Youtrust) covers the full remote-signature lifecycle: document preparation, signatory creation, activation, waiting for the result, and retrieval of final artifacts.
Youtrust sends signing invitations to supplied contacts. The process remains waiting until the request is signed, declined, expired, or canceled.
- The node accepts one or more PDF or DOCX documents and one or more signatories.
- Smart Anchors define signature fields in each document.
- Signed documents and audit trails may be retained as Ormuz files.
Typical scenario
A generated DOCX commercial contract contains one anchor for the customer and another for the company representative. Youtrust invites both contacts in the intended order, then the signed route continues contract activation.
Quick start
Prepare a document with at least one Smart Anchor and bind the contacts who must receive the Youtrust invitation.
Document
- PDF or DOCX accessible to the process
- At least one detectable Smart Anchor
s1,s2, etc. indexes consistent with the signatory list
Signataires
- First name, last name, and email populated
- List order verified
- Authentication appropriate for the signature level
| Parameter | Binding | Role |
|---|---|---|
documents | contract_file | Document rendered by an earlier step |
signers | contract_signers | Contacts in anchor order |
Decision routes
signedRequest signed
All expected signatories signed and Youtrust considers the request complete.
declinedSignature declined
The signatory declined to sign the request.
expiredRequest expired
The deadline was reached before all expected signatures were obtained.
cancelledRequest canceled
The Youtrust request was canceled before completion.
Process example
Send a contract by email, wait for the Youtrust result, then continue according to the terminal route.
Data resolution
The node builds the request from linked Ormuz objects.
| Data | Source or rule |
|---|---|
| Signatory identity | First name, last name, email, and, when available, phone from contact. |
| Field positions | Locations and dimensions carried by Smart Anchors in the documents. |
Ordre s1, s2, … | Contact order in signers. |
| Langue | Default language from the Youtrust configuration when the contact does not provide one. |
Parameters 10
Request and documents
Configuration, name, and documents defining the request.
Signatories and security
Recipients, order, signature level, and authentication.
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 9
Youtrust request
Request, documents, and people tracked at Youtrust.
Decision
Result used to continue or route the process.
signed, declined, expired, or cancelled decision.signed, declined, expired, or cancelled.Documents finaux
Evidence and files available at the end of the lifecycle.
Behavior
Prepare the request
The node creates or reuses the request corresponding to this step and sends documents with Smart Anchor analysis enabled.
Add signatories
Each contact becomes a Youtrust signatory with the configured signature level and authentication.
Send invitations
The request is activated in email mode and Youtrust handles invitations.
Wait for the result
The process remains suspended until the request reaches a terminal state.
Finaliser
The result, documents, and available audit trails are exposed before the route is selected.
Limits and responsibilities
- The document template must contain Smart Anchors corresponding to the expected signatories.
- An incorrect or inaccessible email address prevents the signatory from receiving the invitation.
- A new business attempt after decline, expiration, or cancellation must create a new lifecycle according to your rules.
Troubleshooting
No Smart Anchor detected
Check the syntax, keep the anchor on one line, and use Arial at 10 to 14 px.
A signatory receives nothing
Check their email, signing order, and notification settings in your Youtrust account.
The request remains pending
Check request state in Youtrust and receipt of signature-completion events.
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.