DocuSign

DocuSign turns a form submission into a legally binding signature: pre-filling an agreement from CMS data, hosting the signing ceremony behind a link or iframe, and writing completion status back to your collections. You collect signatures without leaving the site experience you built.

That covers professional services firms sending proposals, real estate teams routing disclosures, HR teams running onboarding, and developers wiring account-opening flows for regulated industries — all without standing up a full backend.

How to integrate DocuSign with Webflow

What is DocuSign? DocuSign is a provider of e-signature and agreement-management software, including Contract Lifecycle Management and Intelligent Agreement Management. Its eSignature product sends and signs documents across devices, with signatures enforceable under the U.S. ESIGN Act. Features like PowerForms, Web Forms, Templates, and DocuSign Connect webhooks support the automation and embedding patterns you'll use in a Webflow build.

Reach for these two together when a website needs to capture intent and then convert it into a signed document. A consultation request becomes a service agreement. A property inquiry becomes a disclosure packet. The work is connecting your form and CMS layer to DocuSign's envelope and signing layer, and you have a few ways to do that depending on how much code you want to write.

There's no official DocuSign app in the Webflow Marketplace. Without a marketplace app, most builds use one of these approaches:

• PowerForms and Code Embed let you place a self-service signing document on a page as a link or iframe with no server-side code.
• Zapier and viaSocket connect form submissions to DocuSign workflows through no-code automation.
• The Webflow Data API and DocuSign APIs give you full control over embedded signing and CMS status sync, but require server-side development.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Embed DocuSign PowerForms with Code Embed elements

PowerForms are the fastest no-code path. A PowerForm is a self-service signing document accessible through a URL, so you can place it on any page without a backend. To create one, you need a DocuSign Business Pro plan, PowerForm Administrator permissions, and a saved template as the basis. Add the result to your site using either a standard link element or the Code Embed element.

To set up a PowerForm, go to the Select a template page in DocuSign, select a template, choose Add selected, then CREATE. Open the PowerForm URL dialog and select the icon to the right of Embed to copy the iframe HTML, or use the actions menu (three dots) and Copy URL for a plain link. Open the Add panel, drop a Code Embed element onto the canvas, and paste the iframe HTML.

This method works for self-service NDAs or waivers that visitors sign on demand. Keep your site branding by loading the signing document inside an iframe, or link to the PowerForm from a button when you prefer a hosted DocuSign page over an inline embed.

Code Embed supports HTML, CSS, and JavaScript only, so it works for hosting a PowerForm but can't run server-side logic or hold API credentials. For mobile experiences, DocuSign recommends a WebView rather than an iframe.

Connect with Zapier or viaSocket

Automation platforms connect your forms to DocuSign envelopes without a custom backend. Take this path when you want a form submission to start a signing flow but don't want to run your own webhook listener.

Verified pre-built connections cover both directions:

• Webflow form submission → create a DocuSign signature request
• Webflow form submission → send a DocuSign envelope using a template
• DocuSign envelope status change → update a Webflow live item
• DocuSign envelope completed → add document details to a Webflow collection

viaSocket documents explicit trigger and action pairs, including:

• New Form Submission in Webflow → Create/Update/Delete Workspace in DocuSign
• New Form Submission in Webflow → Add/Update User to Signing Group in DocuSign
• New Order in Webflow → Create/Update/Delete Workspace in DocuSign

These connectors cover the majority of no-code use cases and remove the need for a backend on simpler flows. For in-page signing or precise CMS field mapping, move to the API path.

Build with the Webflow and DocuSign APIs

The API path gives you full control over envelope creation, embedded signing, and status sync. You'll need server-side development because DocuSign API calls use secret credentials that can't live in client-side code. Run a middleware layer or serverless function between the two platforms.

The main API surface includes:

• The DocuSign eSignature REST API v2.1 handles envelope creation, recipient management, embedded signing views, and document downloads
• The Data API v2 handles CMS collection items and form submissions, while webhooks trigger real-time events, including the form_submission trigger

DocuSign uses OAuth 2.0, including JWT Grant for background automation. On the site side, authenticate with OAuth 2.0 or site API tokens, and request the scopes you need — such as sites:write and cms:write — explicitly.

Generate a DocuSign envelope from a Webflow form submission

This flow starts a signing request the moment someone submits a form. Register a webhook so each submission pushes to your endpoint, then let your backend create and send the envelope.

To implement it:

1. Register the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks, using scope sites:write and a body of { "triggerType": "form_submission", "url": "<your callback endpoint>" }.
2. Verify the payload with the x-webflow-timestamp and x-webflow-signature headers, which carry an SHA-256 HMAC signature, then create the envelope with POST /restapi/v2.1/accounts/{accountId}/envelopes. Include documents, recipient definitions, tab placements, and status: "sent" to send immediately.

Prefer webhooks over polling here. DocuSign enforces a 15-minute minimum between GET polls to any specific URL, so a push model keeps both rate budgets clean.

Embed signing directly in a Webflow page

Embedded signing puts the signing ceremony inside your page rather than sending the signer to email. The recipient must have a clientUserId set at envelope creation time, and you can't add this attribute retroactively.

To set it up:

1. Create the envelope with clientUserId on the recipient object.
2. Call POST /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/views/recipient to generate a one-time signing URL, then load that URL in an iframe or redirect immediately, since it stays valid for only 5 minutes.

Generate the signing URL on demand right before you present it, and never cache it. If you use Focused View, add the DocuSign JavaScript snippet through the Code Embed element or Custom code in head and body tags, and watch for Content Security Policy headers that can block DocuSign domains.

Sync envelope status back to the Webflow CMS

This flow updates a CMS record when a signature completes. DocuSign Connect pushes events to your backend, which then patches the matching CMS item. Your site can't receive DocuSign webhook POSTs directly, so you'll need a separate public HTTPS endpoint.

To implement it:

1. Configure DocuSign Connect at the account level or per envelope through the eventNotification attribute to send events like envelope-completed and recipient-completed.
2. Map envelopeId to the CMS item identifier at envelope creation so you know which record to update. On envelope-completed, send PATCH https://api.webflow.com/v2/collections/{collection_id}/items/live with scope cms:write to update status fields for immediate publication.

Match the fieldData object to your collection schema, and format dates as ISO 8601 strings. Your Connect listener must return HTTP 200 within 5 seconds to meet DocuSign's webhook SLA.

What can you build with the DocuSign Webflow integration?

Pairing DocuSign with your site lets you turn website actions into signed agreements without exporting data or emailing documents manually.

• Proposal signing from a form: When a prospect submits a consultation request, a middleware layer creates a service agreement pre-filled with their submission data and sends it for signature. The client accepts the proposal without a separate email round-trip.
• Real estate agreement workflows: A property inquiry form triggers a listing agreement, buyer representation contract, or disclosure packet routed through DocuSign, so agents move from showing request to signed document in one flow.
• Self-service signing pages: A PowerForm embedded through a Code Embed element gives visitors an NDA or waiver they can sign on demand, hosted inside your page with your branding intact.
• CMS status tracking: DocuSign Connect fires an envelope-completed event, your backend patches the live CMS item, and a client-facing collection page shows each agreement's status as Signed in real time.

If you need more control over embedded signing ceremonies or precise CMS field mapping, the API integration path covers those cases with full flexibility.