How to use

Set up once. Then it runs without you.

Four steps everyone does, then each service adds what it needs. This is the whole thing - what you configure, what the screens look like, and what happens on a record once you stop touching it.

4 stepsShared by every service
+2For Document Generation
+1To add Circularo
+3For end to end

Shared setup

Four steps everyone does once.

Whichever service you take, setup starts the same way. It is done once per template, and the rest runs on its own afterwards.

1Shared

Connect your Salesforce org

Authorise the connection once. Production or sandbox, as many as you use - each keeps its own templates and rules, and nothing crosses between them.

Service 01Service 02Service 03
Connections › New connection
Connection name Acme Production▾
Type Salesforce▾
Environment Production▾
Status Connected▾

No managed package. This is a standard authorised login, so there is nothing for your security team to review.

2Shared

Upload the template you already use

The Word or PDF file your team has been filling in by hand. Nothing is rebuilt - you upload the document as it is.

Service 01Service 02Service 03
Document Templates › New template
New template name Renewal Agreement▾
Select Object Opportunity▾
SF Connection Acme Production▾
Upload Renewal Agreement.docx

Word and PDF both work, and the file keeps its own formatting, styles and letterhead.

3Shared

Say where the values go

Drop Salesforce fields into the document where the values belong. Parent records, child records and conditional sections are all placed the same way.

Service 01Service 02Service 03
Document Templates › Fields to include
{{Account.Name}}{{Amount}}{{CloseDate}}{{Owner.Name}}{{#currency Amount}}{{#if Discount__c}}{{#each OpportunityLineItem}}
Child relationship OpportunityLineItem▾
Filter Logic StageName = Closed Won▾

Field names are checked as you go, with a closest-match suggestion when one is slightly wrong.

4Shared

Choose where it gets filed

Each template decides where its document lands on the record, and what the file is called. The signed copy later returns to the same place with a matching name.

Service 01Service 02Service 03
Document Templates › Configuration
File Source Files (ContentDocument)▾
Document Action Create new▾
Filename Pattern {{Account.Name}} - Renewal - {{CloseDate}}

Notes & Attachments is capped at 25 MB by Salesforce. Pick it and the product tells you before a document is ever too big.

Where the paths split

Then each service adds what it needs.

Service 01 stops when the document is filed. Service 02 hands it to Circularo. Service 03 carries on to signatures and back again. Nothing earlier is redone.

EveryoneSteps 1-4
Connect orgUpload templateMap fieldsChoose filing
Service 01Generation
Trigger or buttonDocument filed
Service 02+ Circularo
Connect CircularoTriggerReady to send in Circularo
Service 03End to end
Connect CircularoSignature marksSigners & protectionSend for signatureSigned copy filed back

Service 01

Getting the document produced.

Two more steps and documents start appearing on records by themselves.

5Service 01

Decide what sets it off

A button someone presses, or a rule that watches the record. Same template either way - only the trigger changes.

Service 01Service 02Service 03
Automation Rules › New rule
Match documents by Template▾
Document Action Last Modified▾
Filter Logic StageName = Closed Won▾
Polling interval 5 minutes▾
Status Active▾

Or skip rules entirely and keep it to a button. Set per template, not per org.

6Service 01

Put the button in Salesforce

Copy the button token from the template and paste it into a Salesforce button or Flow. That token is what ties the button to this template and no other.

Service 01Service 02Service 03
Doc Generator › Flow Setup
Button Token b7f3a2c1-9e04-4d8a-…
Target template Renewal Agreement▾

Paste the button freshly from the template you actually want. A button copied from an older template still carries that template's token - the single most common cause of the wrong document being produced.

Service 02

Bringing Circularo in.

One token, and the document arrives in your own signing account ready to go.

7Service 02

Connect Circularo with one token

Paste one API token from your own Circularo account. From then on the two systems stay in step: documents go across, signing status comes back.

Service 02Service 03
Connections › Circularo connection
Connection name Acme Circularo▾
Base URL https://app.circularo.com
API token ••••••••••••••••••••

Stored encrypted. Signing runs on your subscription, under your organisation's terms - never ours.

Service 03

Letting it run the whole way.

Three more steps: where people sign, how they prove who they are, and the switch that lets it send by itself.

8Service 03

Mark where each person signs

Place the signature marks once, on the template. They travel with the content, so they stay correct when the document grows, shrinks or repaginates.

Service 03
Document Templates
UploadAnchor TagsSignature FieldsConfiguration
Recipients 3 signers▾
Order Sequential▾
Anchor Tags Literal text · 3 found

Anchors follow the text they are attached to, which is why a longer document does not push a signature block onto the wrong page.

9Service 03

Say who signs, and how they prove it

Signers are resolved from the record rather than typed in. Each can be asked for a one-time email code, a password, or both before the document will open.

Service 03
Document Templates › Signers & Protection
Recipients (Email Fields) Opportunity.Owner.Email▾
Email OTP On▾
Share password From Salesforce field▾
Automatic reminder Every 3 days▾

A password that cannot be resolved stops the send and says why, rather than quietly going out unprotected.

10Service 03

Turn on send for signature

The last switch. With it on, the document is generated, sent, signed and filed back without anyone opening an email client.

Service 03
Document Templates › Configuration
Send for signature after generating On▾
Max retries 3▾
Send condition (optional) Set▾

Leave it off and everything still works - you simply send the document yourself.

What happens after

One record, start to finish.

Setup is done. This is what a single document does from the moment the trigger fires.

0s
The trigger fires

Somebody presses the button, or the rule sees the change it was watching for.

+1s
Salesforce is read

The record is fetched with its parents, children and grandchildren - one query, built from the template itself.

+2s
The document is built

Values land in place, conditional sections resolve, repeating tables expand, and the file is named by your pattern.

+3s
It is filed on the record

Into Files or Notes & Attachments, whichever the template says. Service 01 finishes here.

+4s
Circularo receives it

The document arrives in your account with signers, signature positions and reminders already configured. Service 02 finishes here.

then
Signers are asked

Each in the order you set, verifying with a one-time code or password before the document opens. Reminders go out on their own.

on signing
The signed copy comes home

Filed on the same record, in the same store, named after the original - and the status on the record updates.

Watch it done on your own template.

Thirty minutes, against your sandbox. Bring the document you produce most often and you will see all ten steps on your own data before the call ends.

Book a Demo See every feature

Screens shown are illustrations of the product, not live screenshots.