Yes. Krokul CRM integrates with Vchasno and sends an invoice, act or contract from the deal card to Vchasno.EDO as a ready PDF. The document status (signed, rejected or waiting for the counterparty signature) comes back from Vchasno to Krokul. A signed document moves the deal to the next stage. The setup runs on the Krokul API and webhooks.
A manager opens the act on the deal card and clicks «Send to Vchasno». Krokul builds a PDF from your template, names the file by the Vchasno rules with the recipient EDRPOU code and the document number, and uploads it with a POST /api/v2/documents request. Krokul stores the Vchasno document_id on the document.
Krokul regularly calls POST /api/v2/documents/statuses for documents waiting for a signature. Status 7008 means all signatures are collected. The document gets the «Signed» mark, and the deal moves to the stage you set in the settings. Krokul records a counterparty refusal (7006) in the deal feed and creates a task for the owner.
When a company with an EDRPOU code appears in Krokul, Krokul checks it with a POST /api/v2/check/company request. The is_registered field of the reply becomes a mark on the company card, and the manager knows before the contract whether the document can go electronically.
In the connection settings, you choose the document types that Krokul sends to Vchasno as soon as they are created. For B2B, this is usually an invoice after the deal moves to «won» and an act after the work is closed. Each sending appears in the sync log with its result.
| Vchasno | Direction | Krokul | When |
|---|---|---|---|
| Document (POST /api/v2/documents, PDF) | Krokul → Vchasno | Invoice, act, contract from the deal | A click on «Send to Vchasno», or automatically by document type |
| document_id | Vchasno → Krokul | External key and link on the document | Right after the upload |
| Document status (7000–7011) | Vchasno → Krokul | Mark on the document, entry in the deal feed | Polling /documents/statuses on a schedule |
| Status 7008, all signatures | Vchasno → Krokul | Deal stage | When the counterparty has signed |
| Status 7006, refusal | Vchasno → Krokul | Task for the owner | When the counterparty has rejected |
| Company check (check/company, is_registered) | Vchasno → Krokul | Mark on the company card | After a company with an EDRPOU code is created |
document.created or card.won. The x-crm-signature header confirms each delivery, and you check it against your secret.document/api-read, take the template from document/api-print (it returns HTML), turn it into a PDF and upload it to Vchasno with a POST /api/v2/documents request. Link the returned document_id to the Krokul document through externalRef/api-upsert.activity/api-create. On status 7008, move the deal on with a card/api-updateStatus call.Yes. Krokul integrates with Vchasno through its API and webhooks. Documents from a deal go to Vchasno.EDO, the signing status comes back, and the deal moves on when the document is signed.
At the next poll. Vchasno sends no events, so Krokul rereads the statuses of documents waiting for a signature itself and stops once a document is signed or rejected.
Krokul builds the PDF from the same template you print from the document card. The file goes to Vchasno with the name the Vchasno guide requires.
A Vchasno plan with API access and a user token. The sender of the document in Vchasno is the company that owns the token.
The parties sign the document in Vchasno, and Krokul only sends the file and follows the status. The Vchasno API sends no events, so Krokul rereads statuses on a schedule, and the Vchasno guide limits the exchange to ten requests per second per company and files to 15 MB.
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.
Vchasno is a trademark of its owner. Krokul is not affiliated with Vchasno.