Integrations

I get the attached error message when trying to authorize Docusign to save documents to my Google Drive. Any ideas on how to resolve this?

Hi! We are trying to install these two applications in the Salesforce partial sandbox: Docusign Gen for Salesforce and Docusign eSignature for Salesforce, but we only have the option to install them in production. Is this a limitation of the apps, or are we missing something?Our user is an admin in the Salesforce partial environment and has all the necessary permissions.Could it be that we need to first install the packages in production, and then it will allow us to install them in the partial sandbox? We would like to test the functionality before releasing it to production.Looking forward to any valuable information on this.Thank you!Arina 

I need a way to keep the envelopes sent by an ex-employee to be updated when completed, even when the Salesforce user is deactivated.I have tried transferring the envelopes to an existing employee, whose Salesforce user is still active. I republished all these envelopes.Then I deactivated the ex employee. The document was then signed. On DocuSign, I can see that the envelope is marked as completed. But on Salesforce it is still marked as ‘Sent’.Do you have a way or an idea why even after the envelope transfer, it is not updated when completed on Salesforce?Thank you

I tried to trouble shoot this issue doing this task “going to DocuSign enabled entity and clicking "Go To DocuSign" from it ("..." button in the ribbon). ”, didn’t workSystem.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Could not find a Docusign User entity for the current user - transaction creation failed (Fault Detail is equal to Exception details:ErrorCode: 0x80040265Message: Could not find a Docusign User entity for the current user - transaction creation failedTimeStamp: 2024-09-02T11:00:51.5766454ZOriginalException: PluginExecutionExceptionSource: PluginExecution--)

I have (What i think is) a really simple requestI have a Docusign Template I want to register new suppliers.    When an envelope status changes to completed, I want to be able to extract the data from the docusign document such as ‘Entity name’, ‘GST Status’, ‘ABN Number’ etc Once I have this data, populate a SharePoint List with the respective infoUsing the Docusign Power Automate actions, I have tried almost every action, and a combination of Tabs, Custom Fields etc.Nothing seems to work!Can someone please advise what actions / methods I need to use for this? 

Hi all,I am a new for DocuSign developer. I am following the article https://www.docusign.com/blog/developers/automate-even-more-docusign-nintex to setup Send Envelope DocuSign at Nintex however I got the error “Received an error response from the connector: {"errorCode":"INVALID_REQUEST_BODY","message":"The request body is missing or improperly formatted. Could not cast or convert from System.String to API_REST.Models.v2_1.document."}”I am looking for some advice to help resolve my issue. I am truly appreciated!This is how I have setup - Step 1: Docusign setup - completedStep 2: Signing document setup - completedStep 3: Nintex Setup - completed Create the workflow1)Get a File from SharePoint - completed2)Send Envelop - everything is complete except the “body” which I can’t insert any informationThen I have test then got the error like below from Nintex 

I would like to take data from airtable  to put on pdf template or any template. Then would like to take this template that is filled out with this data to be electronically signed with docusign.  For example If I am trying to do a lease renewal for an apartment I have a general template of the renewal that has about 10 places where it takes data from airtable to fill out. Then I need to take this document and be able to get electronic signature and then store the final document on airtable. I also have zapier and can pay for make to help get this done if needed. 

I'm facing a critical issue with the DocuSign eSignature app for Salesforce, and I'm hoping someone can help me troubleshoot it.I've installed the latest AppExchange package for the DocuSign eSignature app, and while I've successfully added the DocuSign button to various native and custom objects, I'm encountering a persistent problem with two specific objects. When I attempt to use the DocuSign functionality on the Contacts object or a custom object called "Enrollments," I receive the following error:"Web service callout failed: Unable to parse callout response. Apex type not found for element quickActions."Here's a brief overview of what I've done so far:Installation and Setup: Installed the latest version of the DocuSign eSignature app from the AppExchange. Button Addition: Successfully added the DocuSign button to several other objects without any issues. Error Encounter: The error only occurs when selecting the Contacts object and the custom "Enrollments" object.I've scoured the w

Hi, I am building out a process that triggers the document envelope from Salesforce and then archives it in a SharePoint site. Is there a way I can retrieve the link to the sharepoint file and bring it back into salesforce? I want to add a link in the Salesforce record to point it to the signed contract. 

I am utilizing a Power Apps cloud flow to send out a single document/envelope to 2 separate recipients, with a separate signature tab for each. I am looking for a way to trigger a flow when one of the individuals sign, but before the envelope is ‘completed’ and update a record in Dynamics365 with a status that recipient1 has signed, and recipient2 is still pending signature. Upon review of the available triggers, I see one for envelope-completed but this is for after both signatures would have been received.Is this possible using the out of the box connector?

At our organization, we have two separate DocuSign accounts (different admins, different software versions) but we exist on the same server so we can transfer users across if they transfer from one work area to another.One work area (eSignature Account A) wants to leverage SharePoint connector for their work in our organization’s enterprise SharePoint solution.  Everyone uses this enterprise SharePoint environment regardless of which DocuSign account for eSignatures they use.Can the connector’s environment be configured for the organization versus one or the other of our eSignature accounts? If a client of eSignature Account B for example asks to leverage the DocuSign connector, can it work for them knowing eSignature Account A is already set-up to use the DocuSign connector?The goal is to configure DocuSign connector for SharePoint’s environment once for anyone in either DocuSign accounts to leverage.  There is a good chance I misunderstand but I have the impression the environment is

I'm getting 'This Account lacks sufficient permissions to use Merge Fields.' when I try to add a merge field while creating a template, does anyone know which permission I should add to the DocuSign user in order to make this work?

We currently have our DocuSign connected to our MeridianLink platform to send out documents via MeridianLink for new account opening and loan documents, etc to be signed electronically. When these documents are sent out, is there a way to set up expiration timeframes and reminder frequency on the DocuSign side, or would this all be controlled through MeridianLink? 

If I am trying to create or modify an envelope template in from Salesforce and get to the “Place Fields”I then receive the following error:  Content was blocked and it says contact the owner of the website. As anything else out the DocuSign part works in Salesforce I can only imagine it happen during accessing DocuSign sites. I already tried different settings in Chrome / Edge / Firefox but still getting the same error.  Any support would be highly appreciated. 

Is Retrieve a Windows app or a browser-based app?  It is unclear from the KB articles and video demos. Maybe a combination of the two?

Hello Community,In Salesforce I generate a PDF which should be send via docusign.In the document I used Anchor Tags like \s1\ for Signer 1 and \s2\ for Signer 2. In the documentation I read that Checkboxes could be implemented via \cb1\ or \cb2\ and text via \txt1\. Also i found an article Use Automatic Anchor Text with Custom Tags (docusign.com) where its stated the implementation needs to be as follow \tbx_1_text\ for text and \cb_1_yes\ for a checkbox. For the secong solution Merge fields need to be created, but I dont need writeback functionality. The customer should only be able to click the checkboxes and fill in some text.Is there any chance to get this working?Also I’m missing an anchor tag for a stamp. Is this possible? Thanks and all the best,Sven 

Hi DocuSign Community,We are utilizing DocuSign Connector from the Power Automate Flow and seeing the following issues. Tab type “Text” is not showing a place holder for signing party. Tab type “Signature” is showing on top of the “tabs anchor string” and it’s overlapping after signing. [Snap attached] Triggers are not working.Note: We are using Microsoft as Account.Thanks,Dharma Reddy B.

I changed language preference on DocuSign web from English to French, however when I access DocuSign add-in from my outlook I still see it in English? How can I change DocuSign Add-in reference? Sharing add-in screenshot for your clarity -  

I want to integrate DocuSign with One trust. Is there any documentation/guide available to implement the same? 

I have been a ZipForms, DocuSign and DocuSign Transaction room user for several years. I have received this error on more than one occasion in the past 6-10 months. Sometimes I have time to wait for it to "clear up" but it's nothing I'm doing wrong. It just refuses to connect. I've refreshed the tabs but it starts when I am using Zip Form to create and tag the docs in a "package" that when I click NEXT it automatically opens a new window in DocuSign and brings the docs in for further tagging before sending out for signing. account.docusign.com refused to connect This is what pops up in the window of DocuSign.

HelloIn power automate I have a flow that uses docusign and I am puttin some tabs on a document. When I start typing on one of the tabs, the same value is entered in all the tabs. The anchors are all different for each tab. Moreover even if I set the tabs to optional they appear as required when I hover over them.   I’ve tried both old and new designer in power automate

I am getting the following error when sending envelopes via Captivate IQ with the DocuSign integration:“ DocusignIntegrationErrorThe user name for the recipient is invalid. The user name is invalid for recipient Id 00000000-0000-0000-0000-000000000000 “Has anyone encounter this issue in the past? I’ve verified my data and everything looks okay. 

Hi community, I am struggling with the following matter:We purchased DocuSign eSignature (no Document Generation).Use CaseOn the Quote record, we generate files (output is either .docx or .pdf) via CPQ Template. In our DocuSign Envelope Template (dfsle__EnvelopeConfiguration__c), we want to add merge fields to these generated files. The documentation from the legacy solution suggests using AutoPlace Fields (also called anchor tags) in our template content (e.g., \s1\ for Signer 1). This solution is not viable for us as it is a legacy feature. I have been trying to find an alternative solution for this matter in the documentation but unfortunately without success. Can anyone help? Thanks. Screenshot 1: Document from Salesforce record (Place Fields step is missing)Screenshot 2: Document from upload (Place Fields step appeared) it regards placing merge fields on a dynamically generated file related to a Salesforce record, in a Docusign Envelope Template record https://www.loom.com/share/0

Could not generate document "test demo on prod": [146] Failed to get SF Access Token with error code BadRequest and error message {"error":"invalid_grant","error_description":"expired access/refresh token"} 

We have recently transitioned from DocuSign eSignature for Salesforce to DocuSign App Launcher. It has come to our attention that certain users who previously had the capability to log in as another user in Salesforce and send a DocuSign envelope on their behalf are now experiencing issues. When attempting this action, the page fails to load properly. This functionality is crucial to our process. We are investigating if there is a specific permission or setting that can be adjusted to restore this capability. Although these users have shared access through the DocuSign website and can send on behalf of others from there, we aim to integrate this feature within our Salesforce organization due to dependent processes. We are seeking a solution to ensure seamless operation and maintain our workflow efficiency.