Real-time
Two-way sync
Changes in Close or Docusign instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Close to Docusign integration — real-time, two-way sync
Keep Close and Docusign in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Close and Docusign
Sync what happens in Docusign with the customer records in Close, in real time and in both directions.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Docusign holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Stacksync connects Tabs (form fields), Envelope Custom Fields, Folders, Users in Docusign to Custom Fields, Users, Smart Views, Leads in Close with bi-directional, real-time sync. Activity and record changes in Docusign update the matching contact or account in Close, and CRM data flows the other way wherever Docusign can store and use it.
Common use cases
- 01 Sync completed Envelopes and their Recipients status into Postgres so operations teams track signature progress and turnaround in SQL without logging into Docusign.
- 02 Create and send an Envelope from a Template when a CRM Opportunity reaches closed-won, then write the returned envelopeId and status back onto the record.
- 03 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
- 04 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
Common sync patterns
Where Docusign supplies contact or company data
Enriched fields land directly on records in Close, and refreshes keep them from going stale.
Where Docusign can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Close sync into Docusign, so people working there have the context without switching tools.
What you can sync between Close and Docusign
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Close objects | Docusign objects | How this pairing syncs | |
|---|---|---|---|
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Users Account members and senders; the eSignature Users resource exposes them for attribution and reporting, while bulk org-wide user provisioning uses the separate Admin API. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Envelopes The core container for a signature request — documents, recipients, routing, and status; read status and metadata two-way, and create/send new envelopes. | Activities is specific to Close and Envelopes to Docusign — each maps to any object or custom field on the other side. | |
| Tasks Follow-up items assigned to users; synced for workload and SLA reporting. | Recipients Signers, carbon copies, and agents on an envelope, each with a routing order and status; read recipient progress, write recipient lists when an envelope is created. | Tasks is specific to Close and Recipients to Docusign — each maps to any object or custom field on the other side. | |
| Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Documents The PDF files inside an envelope plus the certificate of completion; read signed output out to a store, or supply source documents on create. | Custom Activities is specific to Close and Documents to Docusign — each maps to any object or custom field on the other side. | |
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Templates Reusable envelope definitions with predefined recipients and tab placement; read to map fields and referenced by ID to generate new envelopes. | Custom Fields is specific to Close and Templates to Docusign — each maps to any object or custom field on the other side. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Tabs (form fields) Signature, initial, date, text, and checkbox fields on a document; they carry the data a signer entered and are read out into databases. | Smart Views is specific to Close and Tabs (form fields) to Docusign — each maps to any object or custom field on the other side. |
How changes propagate between Close and Docusign
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Close Docusign Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Docusign through its API, with automatic retries and rate-limit backoff.
Docusign Close Sub-second propagation
DetectionDocusign notifies Stacksync of record changes through webhook events. Docusign Connect webhooks push envelope and recipient status-change events in real time.
DeliveryEach detected change is written to Close through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Close: Subject to per-endpoint rate limits communicated in response headers.
- Docusign: Default 3,000 API requests per hour per account across all integrations, plus a burst limit of 500 calls per 30-second window; usage is exposed via the RateLimit and BurstLimit response headers.
What ships with Close ⇄ Docusign
Connect Close and Docusign for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Docusign connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Close or Docusign data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Close or Docusign record.
Observability
Monitoring
Track your Close ⇄ Docusign sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Close and Docusign.
How the Close and Docusign connectors work
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
Docusign
- Integration surface
- eSignature REST API v2.1 (plus Docusign Connect webhooks; separate CLM, Rooms, and Admin APIs)
- Authentication
- OAuth 2.0 — Authorization Code Grant for interactive apps, or JWT Grant (RSA key pair with user impersonation) for server-to-server integrations
- Change detection
- Docusign Connect webhooks push envelope and recipient status-change events in real time; polling is the fallback and is limited to once every 15 minutes per envelope
- Capabilities
- read · write · webhooks
- Rate limits
- Default 3,000 API requests per hour per account across all integrations, plus a burst limit of 500 calls per 30-second window; usage is exposed via the RateLimit and BurstLimit response headers
How it works
How to connect Close to Docusign — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Close and Docusign with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Close
connected
Docusign
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Close and Docusign objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Close ⇄ DocusignCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Close DocusignCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Close and Docusign integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Close and Docusign: authenticate both systems, choose the objects to sync (such as Close's Users and Activities), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Docusign side: Tabs (form fields), Envelope Custom Fields, Folders, Users, plus custom fields where Docusign exposes them. On the Close side: Custom Fields, Users, Smart Views, Leads. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Close and Docusign: Where Docusign supplies contact or company data; Where Docusign can store CRM context: fields kept current. Enriched fields land directly on records in Close, and refreshes keep them from going stale.
-
Close: REST API. Authentication: API key (sent via HTTP Basic auth). Docusign: ESignature REST API v2.1 (plus Docusign Connect webhooks; separate CLM, Rooms, and Admin APIs). Authentication: OAuth 2.0 — Authorization Code Grant for interactive apps, or JWT Grant (RSA key pair with user impersonation) for server-to-server integrations. Stacksync manages authentication, retries, and rate limits on both sides.
-
Docusign: Docusign strictly limits polling to once every 15 minutes per envelope and recommends Connect webhooks instead for detecting status changes. Close: Close's data model is lead-centric: the Lead is a company-level record, and contacts, opportunities, and activities all hang off it, unlike CRMs that treat accounts and contacts as separate top-level objects. Stacksync's field mapping accounts for these differences between Close and Docusign without custom code.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 534 integrations available for Close and Docusign.
Popular · 8 of 534
-
Close ⇄ Microsoft Teams -
Close ⇄ NextGen Healthcare -
Close ⇄ Orderful -
Close ⇄ Resend -
Docusign ⇄ Chorusai -
Docusign ⇄ Clari -
Docusign ⇄ Dun And Bradstreet -
Docusign ⇄ Seismic
No integrations match .
