DocuSign Adhoc Signature Setup in ServiceNow (After OOTB Integration Flow Deprecation)

[Nishi09]

Hi all,

I’m working on integrating DocuSign with ServiceNow for an adhoc signature use case, but I’m facing challenges since the OOTB DocuSign Integration Flow (DT DocuSign Integration Flow) is now deprecated.

My requirement:

• We have created a PDF template using the Document Template module in ServiceNow.
• When a Case is created, a Document Task should be automatically generated and assigned to a user.
• When the user opens the Document Task (from the Service Portal), the PDF template should open.
• The user should be able to sign the document using DocuSign directly within the ServiceNow portal.

What I’m looking for:

• Guidance on the recommended approach to implement DocuSign adhoc signing with the current (non-deprecated) integration options.
• Any best practices for embedding DocuSign signing (recipient view) inside Service Portal.

Questions:

1. Is there a way to embed the DocuSign signing experience within the Service Portal?
2. Are there any updated integrations or spokes replacing the deprecated flow?

Any guidance, documentation, or examples would be greatly appreciated.

Thanks in advance!

[Naveen20]

Use the DocuSign eSignature Spoke + Redirect-based signing.

Setup:

1. Install the DocuSign eSignature Spoke from the ServiceNow Store — it's the official replacement for the deprecated DT flow. Configure OAuth 2.0 outbound connection to DocuSign.

2. Build a Flow Designer flow triggered on Case creation that auto-generates the Document Task with your PDF template attached.

3. In your Service Portal widget, when the user clicks "Sign," make a server-side call that uses the spoke's actions to create an envelope (with the user as an embedded recipient using a clientUserId) and then generate a Recipient View URL. Redirect the user to that URL in a new tab.

4. Set the returnUrl back to your SP page so the user lands back in ServiceNow after signing. Use DocuSign Connect webhooks (via the spoke's inbound triggers on Xanadu+) to update the Document Task status in real time.

Why redirect over iframe? The signing URL is single-use and expires in 5 minutes, which makes redirect simple and reliable. Embedding via iframe introduces CSP conflicts with Service Portal, mobile compatibility issues, and extra domain whitelisting — complexity that isn't worth it for most ad-hoc signing use cases.

[Tanushree Maiti]

Integrating DocuSign with ServiceNow for ad hoc signature use cases involves using the DocuSign eSignature Spoke in ServiceNow’s Integration Hub.

This enables users to send static documents, uploaded as attachments, for signature directly—without the need for preconfigured DocuSign templates.

Regarding your queries, check 

1. The integration of DocuSign with ServiceNow leverages APIs and pre-built connectors to embed eSignature workflows directly into HR service portals

Refer: DocuSign integration with ServiceNow: HR Service Delivery use cases 

2. Stored App: Docusign eSignature Spoke 

    Docusign eSignature Spoke