TrueSign Connect — Writeback
Writeback brings back into Salesforce what the signer entered in the document: tax classification, purchase order number, consent, IBAN… The data collected at signing time lands straight in your fields, with no re-entry.
It fires at envelope completion, never before: an answer the next signer can still change is not an answer.
There are two levels.
1. Simple writeback — the same field, there and back
On a merge field row, tick "Write back to Salesforce". The entered value goes back into the field it came from, on the source record. Nothing else to configure: the row already knows both ends.
No effect on a read-only field — a field the signer cannot modify has nothing to report back.
This is the most frequent case, and the safest: there are no two lists to keep in sync by hand.
2. Advanced writeback — a different field, another object
The Writeback tab sends a document field somewhere else:
| Setting | Role |
|---|---|
| Document field | The label of the field to retrieve — picked from the list of fields declared above, never typed by hand |
| Salesforce field | The destination, picked from a list (only updatable fields are offered) |
| Target object | The source record, the linked Contact, or a custom object |
| Transform | Uppercase, Lowercase, Boolean, or none |
| Trigger | At envelope completion, or as soon as a signer has signed |
A row saved without selecting a trigger will never fire.
3. Value conversion
A document returns text; a Salesforce field expects its own type. Conversion is automatic: checkboxes (true, yes, 1…), amounts (spaces and € are stripped), integers, and dates in dd/mm/yyyy and yyyy-mm-dd formats.
4. Knowing what happened
Every writeback leaves a trace in the request's audit log:
WRITEBACK— the number of records updated;WRITEBACK_FAILED— what was refused, and why.
A misconfigured mapping never prevents the others from succeeding: each record is processed independently. An invalid configuration is in fact refused when the template is saved (non-existent field, not updatable, writeback on a read-only field, duplicate label, missing placement) rather than staying silent until signing day.
5. Full example
A framework contract sent from an Opportunity.
At send time, four fields are pre-filled:
| Document field | Salesforce path | Mode | Result |
|---|---|---|---|
| Client | Account.Name | Read-only | Nord Industries |
| Industry | Account.Industry | Editable | Manufacturing |
| Amount | Amount | Read-only | 24 500,00 € |
| Purchase order | Description | Editable, empty | (to fill in) |
The signer corrects the industry if needed, enters their purchase order number (BC-245556), ticks "Confidential", signs.
At completion, Salesforce is updated:
Opportunity.Description=BC-245556(simple writeback)Account.Industry= the confirmed value (simple writeback, parent path)Opportunity.IsPrivate=true(checkbox)Opportunity.NextStep=BC-245556(advanced writeback, Uppercase transform)
6. Automatic writeback (no configuration)
Independently of mappings, TrueSign always keeps up to date: the status of the request and of each signer, the signing date and counter, and the signed PDF attached to the record — see Download the signed document.
7. Troubleshooting
| Symptom | Most frequent cause |
|---|---|
| Writeback writes nothing | Read-only field, or trigger not selected (§2) |
| It writes on the wrong record | Check the target object: source, linked Contact, or custom |
| A date comes out wrong | The signer typed a free-form format; only dd/mm/yyyy and yyyy-mm-dd are accepted |
| Nothing happens although everything looks right | Check the request's audit log: WRITEBACK_FAILED gives the exact reason |
Writeback only runs on an authenticated event — HMAC signature for the Yousign webhook, the in-org ceremony for weSign. A forged notification cannot write anything into your org. See Security architecture.