Kommo + DocuSign: automating document signing from the sales pipeline

The deal is agreed — but closing is still a long way off. The manager manually creates a contract in DocuSign, fills in the client’s details, sends it for signature, waits, then manually updates the deal status in Kommo. At 30–40 deals per month, this is hours of routine work and a constant risk of sending a document with data errors. A custom Kommo and DocuSign integration closes this gap: the document goes out for signature automatically, and when signed the deal moves to the next stage without the manager’s involvement.

Why there is no native integration

Kommo’s marketplace has no official DocuSign connector. Third-party platforms — Albato, Latenode, viaSocket — offer basic automation but with serious limitations:

• ✅ Sending an envelope from Kommo on a basic trigger
• ✅ Basic envelope status tracking
• ❌ No data transfer from deal fields to DocuSign template fields — details need to be filled in manually
• ❌ No automatic deal stage transition on signing
• ❌ No reverse synchronization: data from the signed document does not return to Kommo contact fields
• ❌ Conditional logic requires writing JavaScript directly in the Latenode interface
• ❌ Rate limits when processing more than 20–30 documents per day

What the Exceltic.dev custom integration solves

• Automatic sending for signature — when a deal moves to the “Send contract” stage, a DocuSign envelope is created and sent automatically without the manager’s involvement
• Prefill from deal fields — client details, contract amount, dates, address, tax ID — all data from Kommo deal fields is populated into the corresponding DocuSign template fields via the Tabs API
• Automatic stage transition — upon receiving the envelope-completed event, the deal in Kommo automatically moves to the “Contract signed” stage
• Reverse data synchronization — fields filled by the signatory in the document (e.g. bank details or project start date) are passed back to custom fields in the Kommo card
• Multiple signatories — the integration supports routing order: client first, then company director, then lawyer — each receives notification at the right moment
• Different templates for different pipelines — the “New clients” pipeline uses one contract template, the “Renewal” pipeline uses another
• Document link in the card — after the envelope is created, its direct link is written to a custom field in the Kommo deal
• Timer-based reminders — if the document is not signed within 48 hours, a task is automatically created in Kommo for the manager

How the integration works — technical process

Connection architecture

The integration is built on the link: Kommo Webhooks → Exceltic middleware → DocuSign eSign API. Authentication with DocuSign is implemented via JWT Grant (Server-to-Server OAuth) — the most reliable method for server integrations without user involvement. Reverse synchronization works via DocuSign Connect Webhooks, which send notifications on every envelope status change: envelope-sent, envelope-delivered, envelope-completed, envelope-declined, envelope-voided.

Data from the signed document is extracted via the DocuSign Tabs API — each template field has a unique tabLabel that maps to the corresponding Kommo deal field in the configuration table.

Step-by-step workflow

1. Manager moves deal to the “Send contract” stage in Kommo
2. Kommo sends a webhook with the deal ID to the middleware endpoint
3. Middleware requests deal data GET /api/v4/leads/{id} and contact GET /api/v4/contacts/{id}
4. The correct DocuSign template is determined by pipeline type from the configuration
5. An EnvelopeDefinition object is built with templateId, array of recipients, and prefillTabs — fields from deal data
6. Envelope is created and sent: POST /v2.1/accounts/{accountId}/envelopes
7. DocuSign returns envelopeId — middleware writes it and the link to Kommo deal custom fields
8. When signed by all parties, DocuSign Connect sends the envelope-completed event
9. Middleware requests filled field data: GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/tabs
10. Data from document tabs is written to Kommo contact custom fields
11. Deal is moved to the “Contract signed” stage: PATCH /api/v4/leads/{id}

Scenario: document not signed on time

1. When the envelope is created, the middleware starts a deferred 48-hour timer
2. If the envelope-completed event is not received within that time — a task is created in Kommo for the manager: “Contract not signed — remind the client”
3. The manager can send a repeat reminder directly from Kommo via Salesbot — this triggers POST /v2.1/accounts/{accountId}/envelopes/{envelopeId}/resend in DocuSign

What happens on error

The DocuSign API returns detailed error codes. The middleware handles the most common scenarios: INVALID_EMAIL_ADDRESS — task for the manager to check the signatory’s email; TEMPLATE_ID_NOT_FOUND — notification to the integration administrator; ACCOUNT_LACKS_PERMISSIONS — immediate notification with a description of the plan issue.

Real case

Recruiting agency, 6 managers, ~80 deals per month, EU clients.

The agency worked with two types of contracts: a staffing agreement (with the client) and an offer letter for the candidate. Both documents were sent manually: the manager created an envelope in DocuSign, copied details from Kommo, waited for the signature, and manually updated the deal status. Each document set took 15–20 minutes.

A separate problem was tracking: at 80 deals per month, managers regularly forgot to follow up on unsigned documents. On average 8–10 deals per month were stuck at the “Awaiting signature” stage for more than a week without a reminder.

After launching the integration, documents are sent for signature automatically when the stage changes. Details are populated from Kommo without manual entry. Unsigned envelopes after 48 hours automatically create a task for the manager. In the first month, the average time from contract sending to signing was reduced from 4.2 to 1.8 days.

Result: 20 hours per month returned to the team, 0 forgotten unsigned contracts, signing cycle cut in half.

Which businesses benefit most

The integration is most relevant for service companies with regular document workflows: recruitment, consulting, law firms, real estate agencies, IT outsourcing. Anywhere that every deal requires a signed contract before work begins.

It is especially valuable for companies with multiple contract types and multiple signatories — routing order and template selection by pipeline type eliminate confusion when working with high document volumes.

Frequently asked questions

Can the Kommo and DocuSign integration be set up via Albato or Latenode? For the simple scenario “send envelope on stage change” — yes. But as soon as you need field prefill from the deal, reverse data synchronization from the document, routing order for multiple signatories, or automatic reminders — these platforms require JavaScript and quickly hit technical limitations. A custom integration via the DocuSign eSign API covers all these scenarios.

Can different DocuSign templates be used for different Kommo pipelines? Yes. The middleware stores a configuration mapping table: Kommo pipeline → DocuSign template. Changing the template for any pipeline is done via configuration without code changes.

What happens if the client refuses to sign the document? On the envelope-declined event, the middleware updates the Kommo deal field and creates a task for the manager with the reason for refusal that the signatory entered in DocuSign. The manager can adjust the terms and launch a new envelope.

Does the integration support multiple signatories? Yes. Routing order is configured: for example, client first, then company director. Each signatory receives notification only after the previous one has completed signing.

How long does it take to develop the Kommo and DocuSign integration? Basic integration with prefill, automatic stage transition, and reminders — 4–6 business days. Version with multiple templates, routing order, and reverse data synchronization — 8–10 business days. Exceltic.dev determines exact timelines after a technical brief.

If you want to automate DocuSign contract sending from the Kommo pipeline — describe your task to the Exceltic.dev team. We will analyze the scenario and propose an architecture for your document workflow.