DocuSign error: INVALIDREQUESTPARAMETER: The request contained at least one invalid parameter.
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!
Page 1 / 2
Hi there @Dries and @Markus_PH,
It looks like our Support Team identified this error as a bug. Our team is aware of the issue and we're working with DocuSign on a fix. I've added your email address as another affected members. That does a few things:
Bring this to the attention of the integration developers
Help track and prioritize fixes
Allows us to notify you via email if/when this is fixed
Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.
Thank you for your patience and understanding.
Hello, @Dries! I dont have a solution yet but i am liaising with Zap Support they have been super helpful and timely in their replies
Once i am able to solve the issue, i will post the solution here! :)
Hi @Clearcare Solutions LTD and @paprel,
I apologize for the late reply here.
It looks like this bug is still open. I have added your vote to the open bug report. While we can’t provide an ETA for the bug’s fix, we will let you know via email as soon as there’s an update.
I appreciate your patience and understanding.
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,
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.
Hi @Niran
Good question.
The error seems to indicate that if you are uploading a Document, then a Name field needs to be filled out.
A field may not be exposed that is required.
That may be due to an issue with how this integration is configured.
I have added you all to the open bug report. We will keep you in the loop via email once the bug has been fixed.
@paprel, I apologize, but the bug is still open. I’d suggest giving DocuSign a nudge regarding the issue since they are the ones who manage and maintain their integration with Zapier.
I really appreciate your patience and understanding.
Hi, same here.
Hi,
Is there any news on this bug ? The Docusign integration seems broken ATM.
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.
This error is happening because the File URL from Google Docs is not valid. Looking at the screenshot, the (file) field here expects the actual file entry:
You may pass on a file using the URL of the file, but the URL needs to be containing the actual file. This means that the file needs to be downloadable.
With that being said, the “Create Document from Template” action doesn’t return the downloadable URL or the file object. You’ll need to add a “Find a Document” step after the “Create Document from Template” step, then mapping the Title of the document from the “Create Document from Template” step to the “Document Name” field in the “Find a Document” step.
After that, you’ll need to map the from the “Find a Document” step to the “Document” field in DocuSign step.
Could you please give that a try, and let me know how it goes?
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.
Hello, @ken.a
Your support is much appreciated I had raised a ticket on the same day i had uploaded this post
I will let you know how the issue gets sorted out
Thank you!
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.
@ken.a please add me to the list of affected users so I can be notified when this is resolved.
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.
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.
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
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!
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 @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.
Hi @chuck1995,
Thanks for reporting this to us.
I have added you to the open bug report as another affected member. We will keep you posted via email once the bug has been fixed.
Thanks!
Hey there,
same issue here:
Uploading a new attachment to Google Drive from Gmail
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?