We have Docusign Envelopes that go out to contacts. The envelopes go out by email but their cell phones are used to authenticate who they are. When I set up a zap to send an envelope, I keep getting this error from Docusign:
RECIPIENT_SMS_AUTH_PHONE_MISSING: SMS authentication phone number cannot be empty.
The receipent’s phone number is mapped in the zap but I feel there is a different field that needs to be mapped. Any suggestions? The AI bot was no help.
+6Hey
The error usually means that you are not passing the SMS authentication field. It’s a specific field and it’s different than the Signed phone number.
Which particular Zapier action you are passing? Does it show a parameter where you can pass this SMS authentication field. If not, then it might be a limitation of the integration.
But there is a workaround by querying the API directly using Webhooks in Zapier action. Here is the API documentation about it here- https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/create. You have to call this particular endpoint- /restapi/v2.1/accounts/{accountId}/envelopes. There you have to send the SMS authentication number in the JSON.
Here is an article about Webhooks in Zapier- https://help.zapier.com/hc/en-us/articles/8496326446989-Send-webhooks-in-Zaps.
I can understand that it’s a bit more technical and complex but if it’s important for you, you can give this approach a try. Hope it helps!
PS: If you need more active help, I’m happy to connect through my Zapier Solution Partner page if you’d like to reach out here- https://zapier.com/partnerdirectory/automation-jinn
+14Hi
Help us have more info by post screenshots showing how your Docusign Zap step is configured along with the encountered error.
+11Hey there
Just seen you reached out to our Support team who replied with an alternative approach to try. Not sure if that sorted it but wanted to share the details from Support’s reply in case it’s helpful for others that might get the same error:
I found that the error you're hitting (
RECIPIENT_SMS_AUTH_PHONE_MISSING) occurs because your DocuSign template requires SMS authentication, but Zapier's "Send Envelope Using Template" action doesn't currently expose a separate SMS authentication phone field to map data to. It only shows the standard Phone field, which isn't enough for DocuSign's SMS requirements.
Here's what I'd like you to test:
- Log into your DocuSign account and open the template used in your Zap (XXXXXXXXXXXXXX)
- Edit the recipient role and disable SMS authentication (switch to email-only delivery)
- Save the template changes
- Test your Zap in the Zapier editor with the updated template to see if it now sends successfully
If that works, the real question is: Would email-only delivery be acceptable for your crew onboarding workflow, or do you need SMS as a requirement?
If that didn’t resolve it, did you have any luck with the Webhooks approach Sparsh suggested?
Let us know what worked, or if you're still stuck at all 🙂
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
