# Adobe Acrobat Sign + Krokul CRM

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.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make.

## What your team gets

### A quote becomes an agreement for signature

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.

### Two signers on the client side

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.

### The last signature moves the deal

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.

### Rejected, recalled or expired

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.

### The signed PDF stays with the deal

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.

## What moves between Adobe Acrobat Sign and Krokul

| Adobe Acrobat Sign | Krokul | Direction | When |
|---|---|---|---|
| Transient document and agreement (POST /agreements) | Quote or contract of the deal, contact as signer | Krokul → Acrobat Sign | The manager sends the document for signature |
| Agreement ID | External key of the Krokul document | Acrobat Sign → Krokul | Right after the agreement is created |
| AGREEMENT_ACTION_COMPLETED | Note in the deal feed with the participant | Acrobat Sign → Krokul | One participant signs or approves |
| AGREEMENT_WORKFLOW_COMPLETED | Document «signed», next deal stage | Acrobat Sign → Krokul | All participants have acted |
| AGREEMENT_REJECTED, AGREEMENT_RECALLED, AGREEMENT_EXPIRED | Deal back to negotiation and a task for the owner | Acrobat Sign → Krokul | The agreement stops without signature |
| Signed PDF (includeSignedDocuments) | File link on the document and the deal | Acrobat Sign → Krokul | With the completion event |

## How to connect today

### Krokul app in Zapier or Make

1. Connect the Krokul app with a Krokul API key, and Adobe Acrobat Sign with your Acrobat Sign account.
2. Start with the Krokul trigger Deal Stage Changed and add the Acrobat Sign action Create an Agreement From Uploaded Document or Create an Agreement From a Library Template.
3. For the way back, start with Agreement Signed by All Participants or Agreement Rejected in Zapier, or Watch Events in Make, and add the Krokul action Change Deal Stage or Create Task.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with scopes for deals, documents and tasks, and register an Acrobat Sign API application for your account.
2. Subscribe to card.statusChanged with webhook/api-upsert and a statusUuid filter for the contract stage. Check the x-crm-signature header of each delivery.
3. Read the document with document/api-read, upload the PDF to /transientDocuments, create the agreement, and store the agreement ID with externalRef/api-upsert.
4. Register an Acrobat Sign webhook for agreement events. On AGREEMENT_WORKFLOW_COMPLETED call card/api-updateStatus, and on a rejection create a task with task/api-create.

**Triggers:** Agreement Created; Agreement Signed by a Participant; Agreement Signed by All Participants; Agreement Rejected; Agreement Recalled; Agreement Expired; Agreement Email Viewed; Agreement Reminder Sent; Agreement State Changed; Agreement Event Occurred; Watch Events.

**Actions:** Create an Agreement From a Library Template; Create an Agreement From Uploaded Document; Upload a Document to Get Document ID; Create a PDF of Signed Agreement; Create a PDF of the Agreement's Audit Trail; Find the Agreement Status; Find the Signing URL; Create an Agreement; Update an Agreement Status.

### For integrators

Acrobat Sign REST API v6 creates agreements from transient documents or library templates, and webhooks are registered through POST /webhooks with a list of agreement events. Before it registers a URL, Acrobat Sign sends a GET with the X-AdobeSign-ClientId header, and the listener echoes that client ID back on every notification. Krokul adds external keys for the agreement ID, card/api-updateStatus for stage moves and signed webhooks with a delivery log.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Adobe Acrobat Sign?

Yes. Krokul works with Adobe Acrobat Sign through the Krokul app in Zapier and Make, and through its API and webhooks.

### Can the agreement use a template from the Acrobat Sign library?

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.

### How does Krokul know which deal an agreement belongs to?

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.

### How does the listener prove it expects Acrobat Sign events?

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.

## Limits

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.

## Related services

- [DocuSign](https://krokul.com/en/integrations/docusign/index.md)
- [Dropbox Sign](https://krokul.com/en/integrations/dropbox-sign/index.md)
- [Google Drive](https://krokul.com/en/integrations/google-drive/index.md)
- [OneDrive and SharePoint](https://krokul.com/en/integrations/onedrive-sharepoint/index.md)
- [Microsoft Outlook](https://krokul.com/en/integrations/microsoft-outlook/index.md)

[E-signature](https://krokul.com/en/integrations/category/esign/index.md)

Adobe, Acrobat and Acrobat Sign are trademarks of Adobe Inc. Krokul is not affiliated with Adobe.

Updated: 2026-10-14

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs