Automation and forms integration · Updated November 15, 2026

Docusign integration

We connect Docusign to your website or app, from a PowerForm link for self-service agreements to envelopes created on your server through the eSignature REST API. Connect webhooks then send signing status back to your CRM or database.

Rated 5.0 out of 5,72 Google reviews

Docusign at a glance

Connects
eSignature REST API, PowerForms, Connect webhooks and OAuth with JWT or authorization code grant.
WordPress
No official plugin on wordpress.org. A PowerForm link, or server code that calls the API.
Webflow
No official app. A PowerForm link; envelopes need a server outside Webflow.
Astro or Next.js with Sanity
A server route creates envelopes with JWT grant; a Connect listener records status.
Custom software
The full eSignature REST API, with production keys only on a paid account.
Complexity
Low for PowerForm links. Medium to high for API envelopes and embedded signing.
Typical setup
1 to 2 days for PowerForms, 5 to 10 days for API envelopes and Connect.

How we connect Docusign

  • WordPress

    As of November 15, 2026, Docusign publishes no plugin on wordpress.org. For self-service forms we link to a PowerForm. For envelopes filled from a WordPress form, a small plugin calls the eSignature REST API from the server with JWT grant, so the private key never reaches the browser. Zapier and Make can also create envelopes from form entries, with less control over templates and errors.

  • Webflow

    There's no official Docusign app for Webflow. We add a PowerForm as a button or link, and signers leave your site for Docusign's signing page. Creating envelopes from a Webflow form needs a server we host, because Webflow can't hold API keys or receive Connect webhooks. Embedded signing inside a Webflow page isn't practical for the same reason.

  • Astro or Next.js with Sanity

    An Astro endpoint or Next.js route handler takes your form, fills a Docusign template and creates the envelope with JWT grant. For signing on your site, it requests a recipient view for a signer with a clientUserId. That link works once and expires after five minutes. A Connect listener updates the record when the envelope completes. Sanity holds page copy and template IDs, not signed documents.

  • Custom software

    The eSignature REST API covers envelopes, templates, recipient views, PowerForms and bulk send. JWT grant suits a single system account; authorization code grant suits users who sign in with their own Docusign account. Production integration keys must belong to a paid or partner account, and some integrations need Docusign's go-live review. Connect posts events to a public HTTPS listener and can sign them with HMAC-SHA256.

What organizations use Docusign for

  • Self-service agreements with PowerForms

    Waivers, consent forms, volunteer agreements and standard NDAs work well as PowerForms. The signer opens a link, enters their email and signs. In email mode Docusign sends a code to verify the address first. Only the first signer starts from the link; anyone after them gets an email.

  • Contracts filled from your own data

    When a client accepts a quote or an applicant is approved, your server fills a Docusign template with their details and sends the envelope. Connect tells your CRM when it's signed, declined or voided, and the signed PDF goes to the record or a document store.

  • Signing inside a portal

    For a client or member portal where people already log in, embedded signing keeps them on your site. Your app authenticates the signer, then requests a single-use signing link. As of November 15, 2026, Docusign's API pricing lists embedded signing only on Enhanced plans, so we confirm the plan first.

What to watch out for

  • Data residency and signature law

    Docusign keeps eSignature data in the region set when the account was provisioned, and Canada is one of five. It can't move data later, and signer names and IP addresses may be copied across regions. E-signatures are valid for most agreements under PIPEDA Part 2 and provincial acts, but wills, some powers of attorney and land transfers are usually excluded.

  • API plan limits

    As of November 15, 2026, Docusign's API plans start at US$50 a month billed annually for 40 envelopes a month (CA$66 on the Canadian page). Intermediate is US$300 for 100 envelopes, and Advanced at US$480 adds PowerForms and bulk send. Embedded signing is listed only on Enhanced, which is custom priced with a five-user minimum.

  • Expired links and missed webhooks

    Recipient view links expire after five minutes and work once, so we generate them when the signer clicks, not ahead of time. Connect retries a failed delivery for about 15 days, but a listener down for longer misses events. We store envelope IDs and check status through the API as a backstop.

Sources

Checked against Docusign's docs on November 15, 2026.

  1. Embedded signing clientUserId, five-minute single-use links
  2. Embedding concepts
  3. PowerForms: create email and direct signing modes
  4. Docusign Connect retry schedule
  5. HMAC security for Connect
  6. Choose an OAuth type
  7. Go-live
  8. Developer API plans API plan prices and features
  9. Developer API plans (Canada)
  10. eSignature plans (Canada)
  11. Data residency five regions including Canada
  12. eSignature legality guide Canada section

Questions about Docusign

Is there an official Docusign plugin for WordPress?

Not on wordpress.org as of November 15, 2026. Plugins that mention Docusign there are third-party form connectors or rival signature tools. We use PowerForm links for simple cases and a small custom plugin that calls the API for the rest.

Can Docusign keep our documents in Canada?

Yes, for eSignature. Canada is one of Docusign's five data regions. Web sign-ups get a region from their location, and accounts set up with a Docusign rep can choose. Confirm the region before you send, since Docusign can't move data afterwards.

Are electronic signatures legal in Canada?

For most agreements, yes. PIPEDA Part 2 covers federal law, and provinces have their own acts, such as Alberta's and B.C.'s Electronic Transactions Acts and Ontario's Electronic Commerce Act. Wills, some powers of attorney and land transfers are usually excluded. Your lawyer makes the call on edge cases.

Should we use a PowerForm or the API?

A PowerForm suits one standard document anyone can sign, with no data from your systems in it. The API suits documents filled from your records, signing inside your app, or status flowing back to your CRM. As of November 15, 2026, PowerForms need a Business Pro or Advanced API plan.

Need documents signed from your site?

Tell us what gets signed, by whom, and where the signed copy should end up. We'll say whether a PowerForm covers it or the API is worth building.

Book a call