E-signature: PandaDoc and Dropbox Sign

Two new e-signature providers in the bring-your-own-account (BYO) model. Paste the credential in Settings, Integrations, enable it, and you can send proposals for signature through them, with the status coming back via webhook. Credentials encrypted, no cost on our side.

PandaDoc and Dropbox Sign (formerly HelloSign) follow the same model as DocuSign, Clicksign and Adobe Sign: you bring your own account (BYO). Documents are created and billed in YOUR provider account, with no cost, margin or intermediation from us. Open Settings, Integrations, find the card, paste the credential (always encrypted) and enable it. Until it is configured and enabled, nothing happens.

When a signature completes and the request is linked to a proposal, the proposal is marked as accepted automatically. If you have more than one e-signature provider enabled, a button for each appears when sending the proposal.

PandaDoc

Sends the document for signature and syncs the status back into the CRM. We upload the document, wait for it to be ready and trigger the signature email to the signer.

1. In PandaDoc (Settings, API and Integrations), generate an API key and paste it into the API key field of the card.
2. Copy the webhook URL and, in PandaDoc, create a document state changed webhook pointing to it; set a Shared Key and paste the same value into the Shared Key field of the card.
3. Enable it. When sending a proposal, choose PandaDoc; the status comes back via the webhook (PandaDoc signs each delivery with the Shared Key, in the signature query parameter, and we verify it).

Dropbox Sign (formerly HelloSign)

Sends the signature request and syncs the status back into the CRM. In Dropbox Sign the same API key authenticates the calls and signs the webhooks (there is no separate secret).

1. In Dropbox Sign (Settings, API), generate an API key and paste it into the API key field of the card.
2. Copy the webhook URL and, in the Dropbox Sign API app settings, set the event callback to that URL.
3. Enable it. When sending a proposal, choose Dropbox Sign; each callback carries an event_hash we verify with your API key (a signature over event_time + event_type).

Neither one costs anything from us: the account and credentials are yours. If a webhook is rejected, check the credential (a Shared Key or API key different from the one stored in the CRM is rejected). If you try to send without having configured the provider, the CRM warns you clearly: the feature stays inert until the credentials are in place.

Open this article inside the system →