Real-time
Two-way sync
Changes in Docusign or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Docusign to Nutshell integration — real-time, two-way sync
Keep Docusign and Nutshell 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 Docusign and Nutshell
Sync what happens in Docusign with the customer records in Nutshell, 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 Envelope Custom Fields, Folders, Users, Envelopes in Docusign to Companies, Activities, Tasks, Notes in Nutshell with bi-directional, real-time sync. Activity and record changes in Docusign update the matching contact or account in Nutshell, 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 Nutshell leads into a warehouse or Postgres so small B2B teams can report on pipeline without exports.
- 04 Push closed-won leads to accounting software to trigger invoicing automatically.
Common sync patterns
Where Docusign can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Nutshell sync into Docusign, so people working there have the context without switching tools.
Where Docusign supplies contact or company data
Enriched fields land directly on records in Nutshell, and refreshes keep them from going stale.
What you can sync between Docusign and Nutshell
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.
| Docusign objects | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Users Rep records used to resolve ownership when syncing assignments | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Envelope Custom Fields Text and list metadata used to tag envelopes for reporting; synced to a warehouse or CRM to key and categorize agreements. | Activities Logged calls, meetings, and emails used for engagement reporting | Envelope Custom Fields is specific to Docusign and Activities to Nutshell — each maps to any object or custom field on the other side. | |
| Folders Containers such as Inbox, Sent, and Draft plus custom folders; listed and moved to organize envelopes and drive reporting queries. | Tasks Rep to-dos mirrored into external work-management or reporting systems | Folders is specific to Docusign and Tasks to Nutshell — each maps to any object or custom field on the other side. | |
| Envelopes The core container for a signature request — documents, recipients, routing, and status; read status and metadata two-way, and create/send new envelopes. | Notes Free-text history attached to leads and contacts, replicated for a full timeline | Envelopes is specific to Docusign and Notes to Nutshell — each maps to any object or custom field on the other side. | |
| 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. | Products Line items attached to leads, used to sync sold products into billing | Recipients is specific to Docusign and Products to Nutshell — each maps to any object or custom field on the other side. | |
| 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. | Tags Segmentation labels mapped to lists or filters in downstream tools | Documents is specific to Docusign and Tags to Nutshell — each maps to any object or custom field on the other side. |
How changes propagate between Docusign and Nutshell
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.
Docusign Nutshell 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 Nutshell through its API, with automatic retries and rate-limit backoff.
Nutshell Docusign Sub-second propagation
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Docusign through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- 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.
- Nutshell: Subject to the platform's API rate limits.
What ships with Docusign ⇄ Nutshell
Connect Docusign and Nutshell for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Docusign–Nutshell connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Docusign or Nutshell 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 Docusign or Nutshell record.
Observability
Monitoring
Track your Docusign ⇄ Nutshell sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Docusign and Nutshell.
How the Docusign and Nutshell connectors work
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
Nutshell
- Integration surface
- JSON-RPC API over HTTPS; a newer REST API is also offered
- Authentication
- HTTP Basic with account email and API key
- Change detection
- webhook subscriptions for record events, with polling as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Docusign to Nutshell — 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 Docusign and Nutshell with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Docusign
connected
Nutshell
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Docusign and Nutshell 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 · Docusign ⇄ NutshellCustomers 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.
Docusign NutshellCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Docusign and Nutshell integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Docusign and Nutshell: authenticate both systems, choose the objects to sync (such as Docusign's Users and Envelope Custom Fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Docusign: JWT Grant integrations require one-time admin consent and impersonate a specific Docusign user, and must respect Docusign's userinfo call-frequency guidance. Nutshell: Authentication uses HTTP Basic with an account email and API key, so no OAuth flow is required for server-to-server sync. Stacksync's field mapping accounts for these differences between Docusign and Nutshell without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Docusign and Nutshell records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Docusign and Nutshell connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Docusign–Nutshell integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Docusign and Nutshell. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Docusign: 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. On Nutshell: Webhook subscriptions for record events, with polling as fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 425 integrations available for Docusign and Nutshell.
Popular · 7 of 425
-
Docusign ⇄ Veeva CRM -
Docusign ⇄ Vtiger CRM -
Docusign ⇄ Zoho SalesIQ -
Docusign ⇄ ZoomInfo -
Nutshell ⇄ Klaviyo -
Nutshell ⇄ Lusha -
Nutshell ⇄ Microsoft 365
No integrations match .
