# Dropbox Sign + Krokul CRM

Yes. Krokul CRM integrates with Dropbox Sign. An agreement from the deal goes to the client as a Dropbox Sign signature request built on your template, Krokul shows when the client opens and signs it, and the final status moves the deal stage. You wire it up with the Krokul app in Zapier, Make or Albato, or with the Krokul API and webhooks.

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

## What your team gets

### An agreement leaves Krokul as a Signature Request

The manager presses Send for signature on the agreement document of the deal. Krokul creates a Dropbox Sign Signature Request from the template linked to that document type, adds the agreement as a PDF, fills the signer from the contact and the custom fields from the deal values. The Signature Request ID is kept on the document.

### The deal feed shows when the client opens it

Dropbox Sign reports when the signer views the request. Krokul writes that moment into the deal feed, so the manager can call while the agreement is open on the client screen.

### All signatures in means the next stage

With several signers, Dropbox Sign reports each signature and then an all-signed event. Krokul notes each signer on the deal and moves the deal to the stage you set only after the all-signed event, so a half-signed agreement never looks closed.

### A declined Signature Request opens a task

If a signer declines, Krokul marks the agreement as declined, returns the deal to the stage you chose and gives the deal owner a task due today.

### The final file is linked once it is ready

Dropbox Sign says when the signed file can be downloaded. Krokul fetches it at that moment, saves it to the file storage connected to Krokul and links it on the agreement and the deal.

## What moves between Dropbox Sign and Krokul

| Dropbox Sign | Krokul | Direction | When |
|---|---|---|---|
| Signature Request from template (signer, fields, PDF) | Agreement document of the deal and its contact | Krokul → Dropbox Sign | The manager sends the agreement for signature |
| Signature Request viewed | Note in the deal feed | Dropbox Sign → Krokul | Dropbox Sign event `signature_request_viewed` |
| Signature Request signed (per signer) | Signer noted on the deal | Dropbox Sign → Krokul | Dropbox Sign event `signature_request_signed` |
| All signed | Agreement status «signed», next deal stage | Dropbox Sign → Krokul | Dropbox Sign event `signature_request_all_signed` |
| Signature Request declined | Agreement status «declined», task, stage back | Dropbox Sign → Krokul | Dropbox Sign event `signature_request_declined` |
| Final file | File link on the agreement and the deal | Dropbox Sign → Krokul | Dropbox Sign event `signature_request_downloadable` |

## How to connect today

### Krokul app in Zapier, Make or Albato

1. Connect the Krokul app with a Krokul API key.
2. Use the Krokul trigger Deal Stage Changed with the Dropbox Sign action Send Signature Request From Template.
3. Start the return path from Signature Request Signed or Signature Request Declined and use the Krokul action Change Deal Stage or Create Task.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key for deals, documents and tasks, and take an API key from the Dropbox Sign API settings.
2. Subscribe to card.statusChanged with webhook/api-upsert, filtered to the agreement stage, and verify x-crm-signature on each delivery.
3. Send the Signature Request from your template, then store its ID on the Krokul document with externalRef/api-upsert.
4. Set your callback URL in Dropbox Sign and reply Hello API Event Received. On signature_request_all_signed call card/api-updateStatus, and on a decline create a task with task/api-create.

**Triggers:** Signature Request Sent; Signature Request Viewed; Signature Request Signed; Signature Request Declined.

**Actions:** Send Signature Request From Template.

### For integrators

Dropbox Sign posts events to an account or app callback URL and expects the reply body Hello API Event Received; any other answer counts as a failure and is retried. The event `signature_request_all_signed` marks that every signer is done, and Dropbox Sign recommends waiting for `signature_request_downloadable` before you fetch the final file. On the Krokul side, the request ID lives as an external key on the document, and signed Krokul webhooks report the stage change to your other systems.

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

## Questions and answers

### Does Krokul integrate with Dropbox Sign?

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

### Is Dropbox Sign the same as HelloSign?

Yes. HelloSign is the former name of Dropbox Sign, and its developer documentation still lives on the hellosign.com domain.

### When does the deal move after signing?

After the all-signed event, which arrives once every signer is done. With one signer it follows the only signature.

### Can I try the connection without sending real agreements?

Yes. Dropbox Sign has a test mode, and its callbacks fire there too, so a Krokul flow can be tested end to end.

## Limits

The signing page, signer reminders and the audit trail stay in Dropbox Sign. Krokul holds the agreement, its signing status and a link to the final file.

## Related services

- [DocuSign](https://krokul.com/en/integrations/docusign/index.md)
- [Dropbox](https://krokul.com/en/integrations/dropbox/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)
- [Gmail](https://krokul.com/en/integrations/gmail/index.md)

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

Dropbox Sign is a trademark of Dropbox, Inc. Krokul is not affiliated with Dropbox.

Updated: 2026-10-12

---

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