Yes. Krokul CRM integrates with Box. Every client company and deal in Krokul has its own Box folder, invoices and contracts issued in Krokul are saved into it, and files that colleagues or clients upload there appear on the deal card as links. Box permissions and retention rules keep governing the content. The Krokul app in Zapier, Make, n8n or Albato runs the link, and the Krokul API with webhooks serves custom builds.
Automation platformsZapierMaken8nAlbato
A new client company in Krokul gets a Box folder under the root you picked, and every deal for that client gets a subfolder named after it. The Box folder ID is stored on the Krokul record. A renamed deal or a moved folder keeps its link.
Box sends FILE.UPLOADED when a file is uploaded or moved into a watched folder. Krokul attaches it to the matching deal as a link with the file name and the uploader. Engineers drop a revised drawing into Box, and the account manager sees it on the deal the same minute.
When Krokul issues an invoice, act or contract, the connector stores it as a PDF file in the deal folder under the document number. Box metadata on the file carries the deal, the client company and the amount, so finance can search Box by those fields.
From the deal, the manager creates a Box file request for its folder by copying your template request. The client opens the link and uploads scans or specifications. Each upload fires FILE.UPLOADED and lands on the deal like any other file.
A contract saved in the deal folder can go out for signature through Box Sign. SIGN_REQUEST.COMPLETED moves the deal to the stage you chose for signed contracts and adds the signed file to it. SIGN_REQUEST.DECLINED returns the deal to its previous stage with a task for the manager.
| Box | Direction | Krokul | When |
|---|---|---|---|
| Folder | Krokul → Box | Client company | A client company is created |
| Subfolder | Krokul → Box | Deal | A deal is created |
| PDF file with metadata | Krokul → Box | Issued document | A document is issued or gets a new version |
| FILE.UPLOADED | Box → Krokul | File link on the deal | A file is uploaded or moved into the deal folder |
| File request (copied from a template) | Krokul → Box | Upload link on the deal | The manager asks the client for files |
| SIGN_REQUEST.COMPLETED, SIGN_REQUEST.DECLINED | Box → Krokul | Deal stage and signed file | A signer finishes or declines |
| COMMENT.CREATED | Box → Krokul | Comment in the deal feed | Someone comments on a file in the deal folder |
Yes. Krokul integrates with Box through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.
No. Files stay in Box with their permissions. Krokul writes its own issued documents into Box and keeps links to the rest.
FILE.UPLOADED. Box sends it for files uploaded or moved into a watched folder, and Krokul matches the folder to the deal through its external key.
Yes. The manager creates a Box file request for the deal folder, and anyone with the link can upload. Box creates new file requests by copying an existing one, so the account keeps one template request.
File contents, versions, collaborators, classification and retention live in Box. Krokul keeps a link, a name and a note for each file and opens the preview in Box.
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.
Box is a trademark of Box, Inc. Krokul is not affiliated with Box.