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.
Automation platformsZapierMakeAlbato
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.
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.
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.
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.
| PandaDoc | Direction | Krokul | When |
|---|---|---|---|
| Document from template (tokens, pricing_tables, recipients, metadata) | Krokul → PandaDoc | Deal, its products, contact and client company | The manager creates a proposal or contract |
| Contact | Krokul → PandaDoc | Contact with email and name | Before the first document for that person |
| document.sent, document.viewed | PandaDoc → Krokul | Note in the deal feed, follow-up task | Event document_state_changed |
| recipient_completed | PandaDoc → Krokul | Note with the recipient who finished | Each recipient completes |
| document.completed | PandaDoc → Krokul | Signed status and next deal stage | All recipients have signed |
| document_completed_pdf_ready | PandaDoc → Krokul | File link to the signed PDF on the deal | PandaDoc stores the final PDF |
| document.paid | PandaDoc → Krokul | Payment fact on the deal | The client pays inside the document |
| document.declined, document.voided | PandaDoc → Krokul | Deal stage back and a task for the owner | A recipient declines or the sender voids |
Yes. Krokul integrates with PandaDoc through the Krokul app in Zapier, Make and Albato, and through its API and webhooks.
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.
PandaDoc changes the document status to document.paid. Krokul records the payment on the deal named in the document metadata.
The document.viewed status adds a note and a follow-up task. The deal stage changes on completion, decline or void.
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.
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.
PandaDoc is a trademark of PandaDoc Inc. Krokul is not affiliated with PandaDoc.
