Best answer

DocuSign error: INVALIDREQUESTPARAMETER: The request contained at least one invalid parameter.

  • 15 November 2023
  • 43 replies
  • 1107 views

Userlevel 1

I am trying to set up a 3 step integration with Monday.com, Google Docs and Docusign Integration. The Monday and GDoc Steps seems to have gone through without an issue. However, after setting all the fields on the Docusign Step, it errors out with this error:

 

Could not create signature request: INVALID_REQUEST_PARAMETER: The request contained at least one invalid parameter. A document was defined without setting the 'name' field.

 

I cant seem to find the ‘Name’ field that is “Invalid”

 

Please find below screenshots for the steps and the fields
if someone could please help me out with this, that would be absolutely fantastic

 

 

 

 

There is one more field and the option to continue to the next step

Below is all of the fields available in the DocuSign Step



But when its time to test it, this is the error I am met with

 

Could you please help me spot the issue?
Thank you!

icon

Best answer by SamB 28 June 2024, 15:28

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

43 replies

Userlevel 7
Badge +6

Hi @sortolo,

I appreciate you reporting this to us.

I have added you to the open bug report. While we can’t provide an exact ETA for the bug’s fix. However, we will keep you in the loop via email once the bug has been fixed.

I appreciate your patience and understanding.

Userlevel 1

Hi @Iroda,

I have added you as another affected member. We will keep you informed via email once the bug has been fixed.

Thank you for your patience and understanding.

 

This bug seem to be open for months now. Please remove this feature from the DocuSign ZAP until the bug is fixed. It doesn’t look too good offering a feature in a paid service that doesn’t work. Not to mention the extra effort caused to clients who try to investigate if they did something wrong.

Thanks in advance,

Userlevel 7
Badge +6

Hi @Iroda,

I completely understand your frustrations and I’m very sorry for the inconvenience this bug has caused you.

I’d recommend relaying this to DocuSign’s Support Team since they are the ones who maintains and manage their integration with Zapier.

I appreciate your patience and understanding.

@ken.a please add me to the list of affected users so I can be notified when this is resolved.

Userlevel 7
Badge +6

Hi @glem,

I have added you as another affected member. We will keep you informed via email once the bug has been fixed.

Thank you.

Hi there! I’d also like to be kept informed about this bug.

In the meantime does anyone have any work arounds? I would also move off Docusign if there was a similar system.

Hi there!

I’ve got this exact same issue, has anyone else found a workaround for this? Extrememly frustrating.

Userlevel 7
Badge +6

Hi @Jon Ashore, and @harrisonking,

I have added you to the open bug report as another affected members. Unfortunately, there are no available workaround for this at the moment. With that said, we will keep you updated via email once the bug has been fixed.

I appreciate your patience and understanding.

Hello @ken.a  any update on this yet?  I tried with Google Drive and Dropbox.  Even went to Docusign and gave permissions to both of those applications.    When using Dropbox and doing a direct download dl=1 vs dl=0 link, it seemed like it really wanted to work but didn’t.   It would be really appreciated if your team is able to resolve this.   

 

If anyone can recommend another application where you can apply a signature request template to a dynamic document, please let me know - thanks!

Userlevel 7
Badge +6

Hi @AMT,

Unfortunately, we can’t provide an ETA regarding for the fix of this bug. This is because DocuSign is managed by their developers who are responsible for updating and maintaining their integration with Zapier. I suggest reaching out to them for any updates regarding this bug.

Moreover, I have added you to the list of affected members. We will keep you informed via email as soon as the bug has been fixed.

Thank you for your patience and understanding.

Hey there,

 

same issue here:

 

  1. Uploading a new attachment to Google Drive from Gmail
  2. Creating an envelope on Docusign

but I receive the same error message as everyone else. Can you add my email to the same open bug report?

Userlevel 7
Badge +6

Hi @rasakl,

I have added you to the open bug report as another affected member. We will keep you in the loop via email once the bug has been fixed.

I appreciate your patience and understanding.

Hey there,

 

Is this bug fixed yet? I am still having the same issue?

Hello, 

Can you add my email to the same open bug report?

I have a the same issue. 

This ticket has been open for about 6 months, would you have any idea of its progress or resolution for other readers please ?

Thank you in advance for your answer 

Userlevel 7
Badge +11

Hi @TitanBen and @Antoine M 👋

Sorry for the delay in a response here. I’ve just checked on the bug report and there’s no updates or any ETAs I can share. But you’ve both been added to the list of folks being impacted so you’ll definitely get a notification from us as soon as DocuSign’s developers have shipped a fix for this issue. 

Hi, @SamB. Can you add me too? Thanks!

@ken.a  Previously said that DocuSign technicians need to address the issue and suggested reaching out to them directly. We did just that, and here is the response: 

"All integrations to Docusign using Zapier are supported through their support teams, as we don't have access to the Zapier integration architecture or troubleshooting tools. I see they mention that support for this issue should be granted from our end, but this is incorrect due to what I mentioned above. If Zapier support provided you with technical reasons please share the information they provided." 


There are a lot of people who would appreciate a solution here. Please help us, Zapier. You are our only hope.

Userlevel 7
Badge +11

You got it, @hs-chris! I’ve added you to the bug report as well so we’ll be in touch by email once it’s resolved.

Thanks for sharing that response from their support team. It appears that the support rep you spoke to at DocuSign isn’t aware that the app was built and is maintained by their own developers. I’ve checked internally and our engineers are in communication with the developers of the DocuSign app to assist them in resolving this. But ultimately we will need to wait for a fix to be implemented on their end.

I’ll be sure to share any updates in the thread here as soon as I have them. Thanks for everyone’s continued patience here in the meantime.

Userlevel 7
Badge +11

Hi folks, I’m very pleased to announce that the bug has been resolved! 🎉

The Docusign team has recently released an update to the Docusign app on Zapier that appears to have fixed these errors. In case you missed the email notification that went out here’s the key details from it that you need to know:

The reason for the error was because the Docusign API needs a file name and there wasn't a place for users to apecify a file name. Now they have added a "Document Name(s)" field to the action. Kindly update your Zap to specify a document name (or map it from a previous step) and publish the changes.


To take advantage of this fix you’ll need to ensure you’re running the latest version of the Docusign app in your Zaps and supply a name for the document as mentioned above. 

That said, if you’re still experiencing issues please do reach out in the Community or get in touch with Support. In the meantime, happy Zapping! 😁⚡