Hi @JonFarmer 

For us to have full context, post screenshots with how the steps are outlined and configured.

@JonFarmer 

For us to have full context, we will need to see how each step is configured in the Zap EDIT mode.

Here you go

@JonFarmer

The recent screenshot is from the Zap VIEW mode, but we need to see screenshots from the Zap EDIT mode, so we’re able to see field types and field descriptions.

@JonFarmer 

The mapped variables have “No data” as the value from the example selected in Step 1, and those fields shown in the screenshot are required and expect a value to be passed.

Make sure to select a Zap trigger example that has representative data.

Help: https://help.zapier.com/hc/en-us/articles/8496310366093

HI

The thing is the name and email fields are what are used to direct Docusign who to send the envelope to. When I run this live the data is passed from Salesforce and the envelope gets sent to the addressed person’s email. So it saying no data is a red herring as this bit works at runtime. The other fields which are hardcoded for the present do not populate on the document itself which is the issue. 

This is the data from a live runtime

templates

templates

1

1

9d7c73cd-88c8-4205-8032-2aec8bf04056

emailSubject

emailSubject

Redacted

emailBlurb

emailBlurb

Please sign the agreement

Host:::Email

Host:::Email

redacted

Host:::Name

Host:::Name

Jonathan Farmer

textTabs::false::Day Of Month

textTabs::false::Day Of Month

11

textTabs::false::Month

textTabs::false::Month

March

textTabs::false::Last Number Of Year

textTabs::false::Last Number Of Year

4

textTabs::false::AP1

textTabs::false::AP1

AP1 Test

textTabs::false::AP2

textTabs::false::AP2

AP2 Test

textTabs::false::AP3

textTabs::false::AP3

AP3 Test

textTabs::false::AP4

textTabs::false::AP4

AP4 Test

textTabs::false::AP5

textTabs::false::AP5

AP5 Test

textTabs::false::AP6

textTabs::false::AP6

AP6 Test

Host|||Redacted|||signersRole|||9d7c73cd-88c8-4205-8032-2aec8bf04056

Host|||Redacted|||signersRole|||9d7c73cd-88c8-4205-8032-2aec8bf04056

1

1

Host:::Email

Host:::Email

redacted

Host:::Name

Host:::Name

redacted

@JonFarmer 

Things to check/try:

• In the Zap step, click the button Refresh Fields]
• Perhaps those DocuSign fields are configured to be populated by the signee, thus ignored when sent by the Zap
• Make sure your DocuSign template is properly configured: https://support.docusign.com/s/document-item?language=en_US&bundleId=gmi1660583110357&topicId=yis1665092718418.html&_LANG=enus

Taking off the required from each field and magically it started to work

Thank you for your assistance.

That’s great news @JonFarmer! A huge thanks to Troy for lending a hand here!

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 

Hey @ken.a & @JonFarmer ,

I’m trying to do the same thing with Docusign - sending data from Airtable to prefill all but the signing fields of a document.  I know this is possible with tabs via the docusign api, but I don’t think you can setup and name custom tabs from the docusign web ui.

It looks like you used a Web Form @JonFarmer.  Is this correct?  You setup up your template with your signer fields, then build a new Web Form from that template, add (and name) all your custom fields you want to prefill, and then push the data from earlier in the zap into the “Send Envelope Using Template…..” step in Zapier?

If this is a web form though, how does it then get sent as an envelope for signing?  That’s the piece I don’t understand.

I’ve been messing around with this for about an hour and think I was missing the web form piece.  Let me know if I’m on the right track!

Thanks!

took me a while to figure out
Turns out, template must have the recipients’ name field filled out when you save it as a template.
Very strange.. but it worked for me.

Thanks so much for sharing the alternative solution you found for this, @careprojecthomes. We really appreciate you taking the time to do that. I’m sure it will be helpful to other folks running into similar issues and stumble across this thread! 

Thanks again and welcome to the Community!  

I am having the same issue! I have tried the above but with no luck. I did write a long post explaining my issue but it was not approved for posting for some reason!

Is there going to be a fix issued for this?

Joe 

Hi @JoeParry83 

Ah, it looks like your previous post had been moved to a brand new topic over here:

I’ll follow up on that other topic soon to help in troubleshooting that error you’re getting. 

@SamB That was for a different error. The main error I am getting is that form data is not being passed through to Docusign from Zapier. the envelope data is but none of the form data is appearing on the DS template. 

Thanks for clarifying that @JoeParry83 and sorry for the misunderstanding on my part previously!

Upon further checking I can see that you’ve been in contact with our Support team and they’ve added you to a bug report for an issue where fields aren’t being filled in when using the Send Envelope Using Template action, which appears to be the main error that you referenced here. 

That bug report is linked to the following Community topic where we’re keeping track of folks who are being affected by the same issue: 

The team are in communication with the Docusign app’s developers and will do all they can from our side to ensure it gets resolved. We can’t make any promises around when their developers will be able to get it resolved it by, but we’ll be definitely email you as soon as they do. In the meantime I’d recommend subscribing to that Community topic to be kept in the loop on any workarounds or updates that are shared there.

For anyone that comes across that thread and wants to be added to the bug report please reach out on the topic linked to this issue and we’ll get you added to it.