Docusign eSignature Spoke - Docusign Connect receives 500 error from ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2025 01:16 PM
Howdy all,
I am working on connecting DocuSign Connect with ServiceNow. ServiceNow is currently connected to the DocuSign API. I have a flow that creates an envelope from a template, fills out the information, adds a recipient, and has DocuSign email it out. I want to use the Wait for Signature from DocuSign action, but I am unable to get any communicaiton back from DocuSign stating when the document is signed. Wondering if anyone has actually had this working before.
The user that was created for authentication has these three roles:
sn_docusign_spoke.docusign_admin
sn_docusign_spoke.docusign_integrator
sn_docusign_spoke.docusign_webhook_answer_subflow_user
This is from the error log on the DocuSign side:
3/20/2025 | 10:10:39 pm
Connect send to: https://instance.service-now.com/api/sn_docusign_spoke/docusign_webhook_rest
3/20/2025 | 10:10:39 pm
Envelope Data:{"event":"envelope-voided","apiVersion":"v2.1","uri":"/restapi/v2.1/accounts/xxx-xxx-xxx/envelopes/xxx-xxx-xxx","retryCount":8,"configurationId":21864997,"generatedDateTime":"2025-03-19T19:34:47.6402727Z","data":{"accountId":"xxx-xxx-xxx/,"userId":"xxx-xxx-xxx/","envelopeId":"xxx-xxx-xxx/"}}
3/20/2025 | 10:10:39 pm
Response: {"error":{"message":"Cannot read property \"status\" from undefined","detail":"TypeError: Cannot read property \"status\" from undefined (sys_ws_operation.1ea8be02788230104b68b0fade5a99d9.operation_script; line 13)"},"status":"failure"}
3/20/2025 | 10:10:39 pm
Response Headers: Transfer-Encoding: chunked --- Connection: keep-alive --- Content-Type: application/json;charset=UTF-8 --- Date: Fri, 21 Mar 2025 05:10:39 GMT --- Set-Cookie: <REDACTED> --- Server: snow_adc --- Server-Timing: sem_wait;dur=0, sesh_wait;dur=0 --- X-Is-Logged-In: true --- X-Transaction-ID: dc2fdd682b9e --- X-Content-Type-Options: nosniff --- Pragma: no-store --- Pragma: no-cache --- Cache-Control: no-cache --- Cache-Control: no-store --- Cache-Control: must-revalidate --- Cache-Control: max-age=-1 --- Expires: 0 --- Strict-Transport-Security: max-age=63072000; includeSubDomains
3/20/2025 | 10:10:39 pm
Error: https://instance.service-now.com/api/sn_docusign_spoke/docusign_webhook_rest :: Error - The remote server returned an error: (500) Internal Server Error.;
Thanks,
Allen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2025 04:42 PM
Hello @AllenN516371355
Seems like what you are sending from ServiceNow to DocuSign is not recognized by DocuSign. If you can share the code then probably it will make more sense to comment further on it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2025 06:08 AM
I don't have any code to share. This is using using the DocuSign site and the DocuSign eSignature Spoke. I was under the impression that if you use DocuSign Connect then it is supposed to work out of the box for receiving envelope status changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 11:42 PM
Please take a look at the Set up a bi-directional webhook for Docusign eSignature Spoke and see if you have configured the step 1 as per the choice of either Legacy or REST 2.1.
Legacy sends the data as XML whereas REST 2.1 will send it as JSON and depending on your configuration the handler should be invoked.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 09:11 AM
Further you need to select "Recipients" under Include Data on the Trigger Events Docusign configuration