E-signatures inside Salesforce, without a managed package
An Opportunity flips to Closed Won and the contract goes out for signature on its own. The signer completes it, and the record updates itself: stage moved, document attached, next step triggered. Nobody opened a new tab, nobody clicked send, and nobody paid for another seat license to make it happen.
A Lighter Way to Add E-Signature to Salesforce
That is the version of Salesforce e-signature integration most teams actually want, and getting there does not require a heavy AppExchange install. Firma.dev connects through the standard Salesforce building blocks your admins already use: Flow, External Services, Apex, and Agentforce. You register it once, wire it into the automations you care about, and signing becomes just another step in the process.
The AppExchange route tends to bundle a managed package, per-seat pricing, and a setup that assumes everyone who touches a contract needs a paid license. For a lot of orgs that math is upside down. A few people send agreements, many people need visibility, and the license count grows regardless.
Ready to build it?
Read the full Salesforce technical guide.
What you can actually do
Three outcomes cover most of what a Salesforce team needs from signing, and none of them require you to write code on the no-code path.
Send for signature automatically from Flow
When a record hits a condition you define, Flow sends the right template to the right signer. Closed Won on an Opportunity, an approved Contract, an accepted Quote, whatever your process keys on.
You register Firma.dev's OpenAPI spec as an External Service one time, and "Create and send signing request" shows up as an action you can drop into any Record-Triggered Flow. This is admin-configurable and does not need a developer for the standard path.
Route the result back to the record
Sending is only half the loop. When the signer finishes, Salesforce recieves a webhook event and the record updates on its own. The Opportunity moves stage, the signed PDF lands on the Contract, the custom object flips to Completed. Your reps see the current state without chasing anyone or checking a seperate dashboard.
Let Agentforce send on request
If you are running Agentforce, you can expose signing as an agent action. A rep asks the agent to send the standard NDA to a contact, the agent confirms the template and signer details, and only then does the request go out.
That confirmation step matters, because these documents reach external parties and you do not want an agent firing off contracts without a human read-back.
The cost difference
The pricing models are the real contrast, so it is worth being plain about them. Firma.dev is pay-as-you-go at €0.029 per envelope (~3¢ USD). No per-seat licenses, no annual minimum, and no contract to negotiate before you send your first document.
Pay for Envelopes, Not Seats
DocuSign for Salesforce is licensed per user per year. That model works against you in the common case where only a handful of people send agreements but the whole team needs to see status. You end up paying for visibility rather than usage. With per-envelope pricing you pay for the documents that actually go out, and nothing more.
Multi-tenant note for ISVs on AppExchange
If you are building an AppExchange app that needs signing for each of your customers' orgs, Customer Workspaces handle the isolation for you. Each customer gets a private workspace with its own templates and its own envelope usage, cleanly separated from every other customer. Setup lives in the Customer Workspaces guide.
How to set it up
The full walkthrough is in the docs, not here. Setting up the Named Credential, registering the External Service, building the Flow, wiring the Apex invocable, adding the Agentforce action, and handling the webhooks back into Salesforce are all documented step by step in the technical guide. This page is the why and the what. The guide is the how.
Full setup, step by step.
Read the full Salesforce technical guide.
