Yes. Krokul CRM integrates with Adobe Acrobat Sign. A contract or quote prepared on a Krokul deal goes out as an Acrobat Sign agreement with the deal contact as the signer. Each participant who signs, rejects or lets the agreement expire leaves a mark on the deal, and the final signature moves it to the next stage. You connect it through the Krokul app in Zapier or Make, or through the Krokul API and webhooks.
Automation platformsZapierMake
The manager finishes a quote on the deal and presses Send for signature. Krokul uploads the document as a transient document, creates the agreement with the contact as the signer and keeps the agreement ID on the Krokul document. Acrobat Sign emails the signer, and the deal shows the agreement as sent.
A supply contract often needs the buyer and the finance director. Acrobat Sign reports AGREEMENT_ACTION_COMPLETED each time one participant finishes. The deal feed shows who has signed so far, and the manager follows up only with the person still holding the agreement.
When every participant has acted, Acrobat Sign sends AGREEMENT_WORKFLOW_COMPLETED. Krokul marks the document as signed and moves the deal to the stage you chose for signed contracts. The required fields of that stage are checked as on any other move.
A rejected agreement, one recalled by the sender or one that expires returns the deal to the negotiation stage. Krokul puts a task on the deal owner that names the event, so the contract is revised or sent again the same day.
With the signed documents option on the completion event, Acrobat Sign includes the final PDF. Krokul saves it to the file storage connected to Krokul, such as Google Drive or OneDrive, and links the file on the document and the deal.
| Adobe Acrobat Sign | Direction | Krokul | When |
|---|---|---|---|
| Transient document and agreement (POST /agreements) | Krokul → Acrobat Sign | Quote or contract of the deal, contact as signer | The manager sends the document for signature |
| Agreement ID | Acrobat Sign → Krokul | External key of the Krokul document | Right after the agreement is created |
| AGREEMENT_ACTION_COMPLETED | Acrobat Sign → Krokul | Note in the deal feed with the participant | One participant signs or approves |
| AGREEMENT_WORKFLOW_COMPLETED | Acrobat Sign → Krokul | Document «signed», next deal stage | All participants have acted |
| AGREEMENT_REJECTED, AGREEMENT_RECALLED, AGREEMENT_EXPIRED | Acrobat Sign → Krokul | Deal back to negotiation and a task for the owner | The agreement stops without signature |
| Signed PDF (includeSignedDocuments) | Acrobat Sign → Krokul | File link on the document and the deal | With the completion event |
Yes. Krokul works with Adobe Acrobat Sign through the Krokul app in Zapier and Make, and through its API and webhooks.
Yes. Acrobat Sign creates agreements from library templates as well as from uploaded files, so a standard contract kept in the library can go out from the deal.
Krokul stores the Acrobat Sign agreement ID as an external key of the document, and the document belongs to the deal. Each webhook event is matched by that ID.
Acrobat Sign counts a notification as delivered only when the listener answers with a 2XX code and returns the X-AdobeSign-ClientId value. Otherwise it retries the delivery.
Signing, authentication of signers, reminders and the audit trail stay in Adobe Acrobat Sign. Krokul keeps the deal, the document and the link to the signed PDF.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Adobe, Acrobat and Acrobat Sign are trademarks of Adobe Inc. Krokul is not affiliated with Adobe.