Real-time
Two-way sync
Changes in Docusign or Folk CRM instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Docusign to Folk CRM integration — real-time, two-way sync
Keep Docusign and Folk CRM 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 Folk CRM
Sync what happens in Docusign with the customer records in Folk CRM, 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 Recipients, Documents, Templates, Tabs (form fields) in Docusign to Custom fields, Notes, Reminders, People in Folk CRM with bi-directional, real-time sync. Activity and record changes in Docusign update the matching contact or account in Folk CRM, and CRM data flows the other way wherever Docusign can store and use it.
Common use cases
- 01 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.
- 02 Extract Tabs data captured from signers — text fields, checkboxes, dates — into a warehouse to populate downstream contract or onboarding tables.
- 03 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
- 04 Keep folk and a billing or customer success tool aligned on company records as deals close.
Common sync patterns
Where Docusign supplies contact or company data
Enriched fields land directly on records in Folk CRM, and refreshes keep them from going stale.
Where Docusign can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Folk CRM sync into Docusign, so people working there have the context without switching tools.
What you can sync between Docusign and Folk CRM
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 | Folk CRM objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Companies Organization records linked to people and kept aligned with billing or CS systems. | Documents is specific to Docusign and Companies to Folk CRM — each maps to any object or custom field on the other side. | |
| Templates Reusable envelope definitions with predefined recipients and tab placement; read to map fields and referenced by ID to generate new envelopes. | Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Templates is specific to Docusign and Groups to Folk CRM — each maps to any object or custom field on the other side. | |
| 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. | Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Tabs (form fields) is specific to Docusign and Custom fields to Folk CRM — each maps to any object or custom field on the other side. | |
| Envelope Custom Fields Text and list metadata used to tag envelopes for reporting; synced to a warehouse or CRM to key and categorize agreements. | Notes Free-text context attached to people and companies, readable for reporting. | Envelope Custom Fields is specific to Docusign and Notes to Folk CRM — 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. | Reminders Follow-up items that can be created from external triggers. | Folders is specific to Docusign and Reminders to Folk CRM — each maps to any object or custom field on the other side. | |
| 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. | People Contact records; the primary entity synced with outreach and enrichment tools. | Users is specific to Docusign and People to Folk CRM — each maps to any object or custom field on the other side. |
How changes propagate between Docusign and Folk CRM
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 Folk CRM 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Folk CRM Docusign Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a 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.
- Folk CRM: Subject to the platform's API rate limits.
What ships with Docusign ⇄ Folk CRM
Connect Docusign and Folk CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Docusign–Folk CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Docusign or Folk CRM 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 Folk CRM record.
Observability
Monitoring
Track your Docusign ⇄ Folk CRM 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 Folk CRM.
How the Docusign and Folk CRM 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
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Docusign to Folk CRM — 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 Folk CRM 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
Folk CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Docusign and Folk CRM 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 ⇄ Folk CRMCustomers 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 Folk CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Docusign and Folk CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Docusign and Folk CRM: authenticate both systems, choose the objects to sync (such as Docusign's Documents and Templates), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. Folk CRM: REST API. Authentication: API key (Bearer token). 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. Folk CRM: Folk's model centers on people and companies organized into shared groups rather than pipeline-first objects, so group membership carries much of the workflow state. Stacksync's field mapping accounts for these differences between Docusign and Folk CRM 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 Folk CRM records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Docusign and Folk CRM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Docusign–Folk CRM integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Docusign and Folk CRM. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 421 integrations available for Docusign and Folk CRM.
Popular · 5 of 421
-
Docusign ⇄ Xactly -
Docusign ⇄ Gong -
Docusign ⇄ Salesforce -
Folk CRM ⇄ Microsoft 365 -
Folk CRM ⇄ Microsoft Dynamics 365
No integrations match .
