Electronic signature (Clicksign)

Send quotes for electronic signature using your own Clicksign account (BYO model).

The Electronic signature integration with Clicksign uses YOUR Clicksign account (BYO model: you bring your own account). Documents are created and billed in your Clicksign account: there is no cost, margin or intermediation on our side. We only wire up the fields and the button to send the quote for signature.

The integration starts inert: nothing happens until you fill in the fields and activate. The access token and the webhook secret are stored encrypted in the CRM and are never displayed back.

Prerequisites

• A Clicksign account (Sandbox for testing or Production) with API permission.
• Access to the Clicksign dashboard to generate the access token (Settings → API) and create a webhook with an HMAC secret.
• In Sellio, administrator access to save the credentials and activate the integration in Settings → Integrations.

What you need to fill in

• Environment: Sandbox (for testing, at sandbox.clicksign.com) or Production (for real, at app.clicksign.com). Each environment has its own access token.
• Access token: the API access token, generated in the Clicksign dashboard under Settings → API. It authenticates the calls (via ?access_token=). It is stored encrypted in the CRM.
• Webhook secret (HMAC): a secret you define when creating the webhook in Clicksign. It is used to verify the HMAC-SHA256 signature of the events Clicksign sends us. It is stored encrypted in the CRM.

How to configure

1. Open Settings → Integrations and find the "Electronic signature (Clicksign)" card.
2. Choose the environment, paste the Access token and the Webhook secret, and click "Save credentials".
3. Copy the "Webhook URL (Clicksign)" that appears and, in Clicksign → Settings → API/Webhooks, create a webhook pointing to that URL using exactly the same secret.
4. Return to the CRM and click "Activate".

How to send a quote for signature

1. Open an opportunity and go to the Quotes section.
2. On the desired version, click "Signature", enter the signer's email (and optionally name).
3. If you have DocuSign and Clicksign active at the same time, two buttons appear ("Send via DocuSign" and "Send via Clicksign"), so choose Clicksign. If only Clicksign is active, a single button already uses it.
4. The CRM creates the document in Clicksign, adds the signer and requests the signature; Clicksign sends the signature email to the signer.
5. As the signer progresses, the status appears in the quote's "Signatures" list (Sent → Delivered → Signed).

How to test

1. Use the Sandbox environment with the sandbox access token.
2. On a quote, click "Signature", enter your own email as the signer and confirm.
3. Confirm that you received the Clicksign email and that the "Signatures" list shows "Sent".
4. Sign the document and check that the status advances to "Signed" and the quote is marked as accepted, a sign that the webhook (with valid HMAC) arrived.

Troubleshooting

• 401 when sending: the access token is wrong or from another environment (a sandbox token used in production, or vice versa). Confirm the environment and re-paste the token for that environment.
• The status does not update on the quote: the webhook is not arriving or the signature fails. Confirm the webhook in Clicksign points to the "Webhook URL (Clicksign)" and uses EXACTLY the same secret saved in the CRM (Content-Hmac header, HMAC-SHA256).
• Event rejected (invalid signature): the webhook secret differs between Clicksign and the CRM. Save the same value on both sides.
• Nothing happens when sending: the integration is inert for lack of credentials or was not activated. Fill in environment + token + secret and click Activate.

Open this article inside the system →