Skip to main content
Best answer

Failed to create an envelope using document in DocuSign

  • 29 February 2024
  • 10 replies
  • 89 views

Trying to use the Docusign connector but get the following error message

 

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.

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

10 replies

Userlevel 7
Badge +14

Hi @JonFarmer 

For us to have context, we will need to see screenshots with how the step is configured.

Userlevel 1

 

Userlevel 7
Badge +14

@JonFarmer 

The Document field expects a file object or a file url, instead of a filename.

Help article about sending files in Zaps: https://zapier.com/help/create/basics/send-files-in-zaps

 

You may want to use a different DocuSign action.

 

Userlevel 1

Hi

I Have uploaded the file to onedrive and shared it via a URL. However now  I get there following error. 

 

Failed to create an envelope using document in DocuSign

The app returned "<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'><html xmlns='http://www.w3.org/1999/xhtml'><head><meta content='text/html; char...". <!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'><html xmlns='http://www.w3.org/1999/xhtml'><head><meta content='text/html; charset=utf-8' http-equiv='content-type'/><style type='text/css'>body { font-family:Arial; margin-left:40px; }img { border:0 none; }#content { margin-left: auto; margin-right: auto }#message h2 { font-size: 20px; font-weight: normal; color: #000000; margin: 34px 0px 0px 0px }#message p { font-size: 13px; color: #000000; margin: 7px 0px 0px 0px }#errorref { font-size: 11px; color: #737373; margin-top: 41px }</style><title>Microsoft</title></head><body><div id='content'><div id='message'><h2>The request is blocked.</h2></div><div id='errorref'><span>Ref A: 40B381CDD5904B0096CB95072987ED24 Ref B: BN3EDGE0513 Ref C: 2024-03-01T11:34:33Z</span></div></div></body></html>

Userlevel 7
Badge +14

@JonFarmer 

We would need to see updated screenshots with how your Zap step is configured to have full context.

Userlevel 1

@JonFarmer

We would need to see updated screenshots with how your Zap step is configured to have full context.

 

The configuration is exactly the same as the previously posted one. The difference is that I deleted the action and re-set it up again. I am also now using a developer account. If you look at the latest error message it is saying that the request is blocked. Does anyone know what that means? Is it that the type of Docusign account does not have privileges for this type of action? That is all I can think of with out any further information in the error message

Userlevel 7
Badge +14

@JonFarmer 

Help articles to reference for using DocuSign in Zaps: https://zapier.com/apps/docusign/help

 

 

Running into the exact same problem. Document is missing required field ‘Name’

In my case however I added a pdf that I found in a previous action on Google Drive. The other fields are correctly filled out. Trust me I tried every combination of email, name and role in both my DocuSign template as in the DocuSign action. (Other DocuSign actions I’ve working fine in other Zaps).

I’m beginning to think this is a bug, so I’m curious to a working example to see what’s different. Any help is much appreciated! 🙏🏻

 

 

Userlevel 7
Badge +14

@Willem_Zap 

If you suspect a bug, then you should open a ticket with Zapier Support: https://zapier.com/app/get-help

Userlevel 7
Badge +11

Hi @JonFarmer and @Willem_Zap. 👋

It appears you’re both running into the bug that’s been discussed in Community here:

I can’t provide an ETA but I’ve added you both to the list of affected members which helps to increase it’s priority and ensures that you’ll both get an email notification from us as soon as it’s been resolved.

As there’s already an existing thread discussing this issue in Community I’m going to close this one out so that we can keep track of everyone being affected by this issue in a single place. For anyone who comes across this post and wants to be added to the notification list please reach out in the main thread here and we’ll get you added! 🙂