Pipedrive · CRM · Planned
Pipedrive deals at the contract stage, signed and noted.
When a Pipedrive deal reaches your contract stage, its person is sent your agreement; when they sign, a note on the deal says so. Today through Zapier or Make.
Today Pipedrive works through Zapier or Make, which run on Free.
Why connect Pipedrive
Three moments this is for.
The deal you send
Press Send for the deal and choose the agreement. The deal's person is sent it, filled from the deal, and nobody copies a name between tabs.
The note on the deal
Signed: a note lands on the deal with the document, who signed it and when, so the salesperson sees it where they already work.
The decline you hear about
The signer declines and says why. The reason is on the deal as a note the same day, before anyone chases a signature that is not coming.
How it works
Today: an automation
Pipedrive's Updated Deal Stage trigger in Zapier, or Watch Deals in Make, runs SignSealer's Send a Form to Sign.
The signature comes back
SignSealer's Document Completed or Document Declined trigger runs Pipedrive's Create Note on the deal.
Built, waiting on our app
A native connection through SignSealer's own Pipedrive app, which registers its own webhook and writes the note itself.
What it can do
Each thing the connection does, and where it stands today.
Send from the deal
Built, not connectable yetPaste a deal's address on the connection's page and choose what goes: any of your templates and forms, or what your rules say the deal needs, to its person or everyone on it, won deals included.
Or at a stage you choose
Built, not connectable yetOff unless you turn it on: an open deal reaching a stage you name sends its person, then its participants, what they owe.
Who signs
Built, not connectable yetThe deal's person first, then its participants.
Your documents read the deal
Built, not connectable yetThe deal's title, value, currency, stage and pipeline are facts your agreement and your rules can read.
A lost deal stops it
Built, not connectable yetA deal marked lost, or deleted, voids what nobody has signed. A deal marked won is left alone.
A note on the deal
Built, not connectable yetWhen everything is signed, or one is declined, a note on the deal says so, with each document, who signed it, when, and a link to it.
The signed PDF on the deal
Built, not connectable yetWhen everything is signed, each signed PDF, sealed with its certificate, is added to the deal's files, where the salesperson already looks. A switch on the connection turns it off.
The deal moves on when signed
Built, not connectable yetChoose won and a signed deal is marked won, or name a stage to move it to; name a deal field of your own, text or with Signed and Declined as its options, and it says which. Both are off until you fill them in on the connection.
A panel inside Pipedrive
Not yetA panel on the deal in Pipedrive itself, so nobody leaves Pipedrive to press Send, is not built yet: it comes with SignSealer's Pipedrive app.
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 Pipedrive, and what SignSealer does with it.
| From Pipedrive | Used for |
|---|---|
| Deal, its person and its participants | Who signs, and the values filled into the agreement |
| Deal stage and status | A lost or deleted deal stops the agreement; a stage you choose can start it |
| Completed, declined | What the note on the deal says |
Where it stands: planned
Built, and not yet connectable. The native connection is written against Pipedrive's documentation and tested against stand-ins: you press Send for a deal and choose what goes, or name a stage that sends it, to its person and participants, a lost or deleted deal voids what nobody signed, and a note goes on the deal when they have signed. It has not run against a live Pipedrive account, and it cannot be connected until SignSealer's Pipedrive app exists and passes Pipedrive's Marketplace review. 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 Pipedrive's Updated Deal Stage, then SignSealer's Send a Form to Sign. In Make: Watch Deals, then Send a Form to Sign.
Step 2
A second Zap or scenario: SignSealer's Document Completed, then Pipedrive's Create Note on the deal.
Step 3
Use the deal ID as your reference so each document leads back to its deal.
Read the full Pipedrive guide How requirements decide what is sent
Questions
Which stage sends the agreement?
Today, whichever stage your Zap or scenario watches. The native connection sends when somebody presses Send for the deal, and also from any stages you name, by the name Pipedrive shows or by number: every Pipedrive company's stages are its own.
Who signs: the contact person, or everyone on the deal?
Today, whoever your Zap sends to, usually the deal's person. The native connection sends to the deal's person first and then to each of its participants.
Will it change the deal's value or status?
Its value, never. With the native connection a signed deal can be marked won or moved to a stage you name, and a field of your own can say Signed or Declined; both are off until you fill them in on the connection. Today, moving a signed deal is a step you add to your own Zap or scenario.
Is SignSealer in the Pipedrive Marketplace?
Not yet. It will be listed when SignSealer's app passes Pipedrive's review, and this page will say so then.
Ready when the next guest is.
Free for the first 10 agreements a month. No card to start.