Salesforce · CRM · Planned
Opportunities at the contract stage, signed and noted.
When an opportunity reaches your contract stage, its contact roles are sent the agreement, and a task on it says when they sign. Zapier or Make until it is live.
Today Salesforce works through Zapier or Make, which run on Free.
Why connect Salesforce
Three moments this is for.
The button on the opportunity
The contract is ready: press SignSealer's button on the opportunity and choose it. Its primary contact, and every other contact role on it, is sent the agreement, filled from the opportunity.
The task on the opportunity
Signed: a completed task lands in the opportunity's activity listing each document, who signed it and when, with a link to it, so the account executive sees it without leaving Salesforce.
The opportunity that is lost
It moves to Closed Lost, or is deleted. What nobody has signed yet is withdrawn, so a customer who walked away is not chased for a signature.
How it works
Today: an automation
Salesforce's Updated Field on Record trigger in Zapier, watching Stage, or Watch Records in Make, runs SignSealer's Send a Form to Sign.
The signature comes back
SignSealer's Document Completed trigger creates a note or a task on the opportunity: Create Record in Zapier, Create a Record in Make.
Built, waiting on our app
Your admin installs SignSealer's Salesforce package once, then you connect with a button. An Outbound Message and a Flow tell SignSealer when an opportunity's stage changes, and SignSealer also looks every hour for anything they missed.
What it can do
Each thing the connection does, and where it stands today.
Send from the opportunity
Built, not connectable yetA button on the opportunity, which your admin adds with the address the connection's page gives you, opens SignSealer to choose what goes: any of your templates and forms, or what your rules say it needs, to its primary contact or every contact role.
Or at a stage you choose
Built, not connectable yetOff unless you turn it on: an opportunity reaching a stage you name, such as Negotiation/Review, sends its contact roles what they owe.
Who signs
Built, not connectable yetThe opportunity's contact roles, the primary contact first.
Your documents read the opportunity
Built, not connectable yetThe opportunity's name, close date, stage, amount, currency and type are facts your agreement and your rules can read.
A lost opportunity stops it
Built, not connectable yetAn opportunity moved to Closed Lost, or deleted, voids what nobody has signed. Closing a signed one as won changes nothing.
A note on the opportunity
Built, not connectable yetWhen everything is signed, or one is declined, a completed task on the opportunity says so, with each document, who signed it, when, and a link to it.
The signed PDF on the opportunity
Built, not connectable yetWhen everything is signed, each signed PDF, sealed with its certificate, is added to the opportunity's files. A switch on the connection turns it off.
The opportunity moves on when signed
Built, not connectable yetName a stage, such as Closed Won, and a signed opportunity is moved there; name a field your admin adds and it says Signed, or Declined when somebody declines. A validation rule that refuses either is said in the connection's activity, and the task still goes.
The signed PDF and its certificate
TodayEach signed document is sealed with a certificate anyone can check, and kept in SignSealer. Zapier's Document Completed hands the PDF on, to an email or to wherever you keep documents.
What comes across
What arrives from Salesforce, and what SignSealer does with it.
| From Salesforce | Used for |
|---|---|
| Opportunity and its contact roles | Who signs, the primary contact first, and the values filled into the agreement |
| Stage, amount and currency | What your documents can read; a lost or deleted opportunity stops it, and a stage you choose can start it |
| Completed, declined | What the task on the opportunity says |
Where it stands: planned
Built, and not yet connectable. The native connection is written against Salesforce's documentation and tested against stand-ins: a button on the opportunity sends what you choose to its contact roles, or a stage you name does, one that is lost or deleted voids what nobody signed, and a completed task goes on the opportunity when they have signed. It has not run against a live org, and it cannot be connected until SignSealer's Salesforce app exists, as a package your admin installs. It needs an edition with API access: Enterprise, Unlimited, Performance or Developer, or Professional with the API added. Until then Zapier and Make carry both directions, and the guide has the exact steps.
Start today
What you can do now, without waiting.
Step 1
In Zapier: trigger on Salesforce's Updated Field on Record for Opportunity, watching Stage, then SignSealer's Send a Form to Sign. In Make: Watch Records, then Send a Form to Sign.
Step 2
A second Zap or scenario: SignSealer's Document Completed, then a note or task created on the opportunity.
Step 3
Use the opportunity ID as your reference so each document leads back to its opportunity.
Read the full Salesforce guide How requirements decide what is sent
Questions
Who signs: the account, or the people on the opportunity?
The people on it. The native connection sends to the opportunity's contact roles, the primary contact first, up to twenty of them. Add the people who sign as contact roles, as most Salesforce orgs already do for a deal's decision makers.
Does my admin have to set anything up?
A few things, once. They install SignSealer's Salesforce package, which Salesforce requires before anybody in your org can connect an app like ours, and add SignSealer's button to the opportunity's page. Then, for speed, an Outbound Message on Opportunity and a record-triggered Flow that sends it when the stage changes, which the guide walks through in a few minutes. Without those SignSealer still looks for changed opportunities every hour, so an agreement goes within the hour rather than within the minute.
Will it change the opportunity's amount, stage or close date?
Its amount and close date, never. Its stage only if you name one on the connection, such as Closed Won, and a field your admin adds can say Signed or Declined; both are off until you fill them in. A validation rule that refuses the change is said in the connection's activity, and the task still goes.
Which Salesforce editions does it work with?
Any edition with API access: Enterprise, Unlimited, Performance and Developer include it, and Professional has it as an add-on. Professional has no outbound messages, so there SignSealer finds a changed opportunity within the hour rather than the minute. Essentials and Professional without the add-on cannot be connected, and Zapier's Salesforce app needs the same access.
Ready when the next guest is.
Free for the first 10 agreements a month. No card to start.