# PandaDoc + Krokul CRM

Yes. Krokul CRM integrates with PandaDoc. A manager creates a PandaDoc proposal or contract from a Krokul deal, with the deal products in the pricing table and the client contact as the signer. When PandaDoc reports the document as viewed, completed, paid or declined, Krokul records it on the deal and moves the stage. The connection runs through the Krokul app in Zapier, Make and Albato, or through the Krokul API and webhooks.

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

## What your team gets

### A proposal with the deal products

On the proposal stage, the manager picks a PandaDoc template for the deal. Krokul creates the document from the template with the client company and deal number as tokens, puts each deal line into the pricing table with its name, SKU, quantity and price, and adds the contact as a recipient in the signer role. The deal UUID travels in the document metadata. PandaDoc returns the document ID.

### Sending waits for the draft

A new PandaDoc document starts as document.uploaded and becomes document.draft a few seconds later. Krokul waits for the draft status and then sends the document with your subject and message. The deal feed records who received it and when.

### A viewed document starts the follow-up

The document_state_changed event with the status document.viewed reaches Krokul when the client opens the proposal. Krokul adds a note to the deal and creates a call task for the owner. The manager calls while the client is reading.

### Completed and paid documents close the loop

When every recipient has signed, document.completed moves the deal to the stage you set for signed contracts, and document_completed_pdf_ready gives Krokul the final PDF to link on the deal. If the template collects a payment, document.paid records the payment fact on the deal. A declined or voided document moves the deal back and creates a task.

## What moves between PandaDoc and Krokul

| PandaDoc | Krokul | Direction | When |
|---|---|---|---|
| Document from template (tokens, pricing_tables, recipients, metadata) | Deal, its products, contact and client company | Krokul → PandaDoc | The manager creates a proposal or contract |
| Contact | Contact with email and name | Krokul → PandaDoc | Before the first document for that person |
| document.sent, document.viewed | Note in the deal feed, follow-up task | PandaDoc → Krokul | Event document_state_changed |
| recipient_completed | Note with the recipient who finished | PandaDoc → Krokul | Each recipient completes |
| document.completed | Signed status and next deal stage | PandaDoc → Krokul | All recipients have signed |
| document_completed_pdf_ready | File link to the signed PDF on the deal | PandaDoc → Krokul | PandaDoc stores the final PDF |
| document.paid | Payment fact on the deal | PandaDoc → Krokul | The client pays inside the document |
| document.declined, document.voided | Deal stage back and a task for the owner | PandaDoc → Krokul | A recipient declines or the sender voids |

## How to connect today

### Krokul app in Zapier, Make or Albato

1. Connect the Krokul app with a Krokul API key.
2. Pair the Krokul trigger Deal Stage Changed with the PandaDoc action Create Document and map the deal fields to the template tokens.
3. Start the return path from the PandaDoc trigger Document Completed, Document Paid or Document Status Changed, and finish with the Krokul action Change Deal Stage, Create Payment or Create Task.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with scopes for deals, contacts, payments and tasks.
2. Subscribe to card.statusChanged with webhook/api-upsert and a statusUuid filter for the proposal stage, and validate the x-crm-signature header of every delivery.
3. Read the deal with card/api-read, create the PandaDoc document with POST /public/v1/documents, wait for document.draft, then call the send endpoint. Store the PandaDoc document ID with externalRef/api-upsert.
4. Add a PandaDoc webhook subscription for your listener. On document.completed call card/api-updateStatus, on document.paid call payment/api-create with the deal UUID from metadata.

**Triggers:** Document Completed; Document Status Changed; Document Paid; Document Sent.

**Actions:** Create Document; Create or Update Contact; Create Attachment; Find Document; Get Document by ID.

### For integrators

PandaDoc signs each webhook with a HMAC-SHA256 of the raw body under the shared key of the subscription. The value arrives in the signature query parameter of the POST URL. Document creation is asynchronous. A document can be sent only in document.draft, and a template with an approval workflow stops at document.waiting_approval first. On the Krokul side, the public API moves deals with card/api-updateStatus, records payments with payment/api-create and keeps the PandaDoc document ID as an external key.

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

## Questions and answers

### Does Krokul integrate with PandaDoc?

Yes. Krokul integrates with PandaDoc through the Krokul app in Zapier, Make and Albato, and through its API and webhooks.

### Do the deal products appear in the PandaDoc pricing table?

Yes. Each deal line becomes a row of the pricing table in your template with name, SKU, quantity and price. The template defines the columns, so the column names in the template must match.

### What happens when the client pays inside the PandaDoc document?

PandaDoc changes the document status to document.paid. Krokul records the payment on the deal named in the document metadata.

### Can the deal move when the client only opened the proposal?

The document.viewed status adds a note and a follow-up task. The deal stage changes on completion, decline or void.

## Limits

Template design, the PandaDoc editor, signing, approval workflows and payment collection stay in PandaDoc. Krokul holds the deal, its products, the buyer and a 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)
- [Adobe Acrobat Sign](https://krokul.com/en/integrations/adobe-acrobat-sign/index.md)
- [Google Drive](https://krokul.com/en/integrations/google-drive/index.md)
- [Stripe](https://krokul.com/en/integrations/stripe/index.md)

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

PandaDoc is a trademark of PandaDoc Inc. Krokul is not affiliated with PandaDoc.

Updated: 2026-10-15

---

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