Sending Secured Signing Requests Using Flow Designer

Overview

This article explains how to send an outbound REST request with the multipart/form-data content type using Flow Designer in ServiceNow.
It builds on the setup described in Integrating Secured Signing API with ServiceNow, so make sure that connection is already configured and tested before continuing.

Note: This method was explored during the proof of concept but was not implemented due to setup errors and limited time to troubleshoot. The working solution used Approach 2 instead. If time allows, you can revisit this method for future exploration or improvement.

---

Background

In the organisation I worked with, the goal was to streamline digital document signing within ServiceNow without relying on external tools.

Secured Signing provides a straightforward API that allows ServiceNow to generate and send documents for electronic signing directly from HR or case workflows.

The initial plan was to build the integration entirely through Flow Designer using the Integration Hub HTTP Connector, sending requests to Secured Signing in multipart/form-data format.

This was intended to keep the solution codeless and maintainable, but during testing we encountered configuration issues that prevented the request body from generating correctly.

---

Configuration steps

Before starting, confirm that your Secured Signing API connection has been created and tested following the instructions in my other blog:

Integrating Secured Signing with ServiceNow

Once confirmed, complete the additional setup below.

---

1. Create the Connection Alias

1. Navigate to IntegrationHub > Connections & Credentials (sys_alias.list).
2. Click New.
3. Fill in the fields as shown:

Ref	Field Name	Value
01	Name	SecuredSigning
02	Connection Type	HTTP
03	Default Retry Policy	Default HTTP Retry Policy

4. Click Submit, then reopen the record for editing.

---

2. Create the HTTP Connection

1. In the Connections tab, click New.
2. Complete the following fields:

Ref	Field Name	Value	Comments
01	Name	SecuredSigning HTTP Connection	Use a clear name ending in HTTP Connection for easier reference.
02	Credential	SecuredSigning OAuth Credential	Select the credential created earlier.
03	Connection URL	https://api.dsx.co.nz/web/v1.4	Secured Signing API endpoint.

3. Click Submit to save your changes.

---

3. Build the Flow

Once your connection is ready, you can add the Action Step to your flow:

1. Open your target flow (for example, Send Document for Signing).
2. Add an Action Step and choose HTTP Request.
3. Select your Secured Signing HTTP Connection alias.
4. Set the Content Type to multipart/form-data.
5. Map the request body fields according to the Secured Signing API documentation.
6. Test the action and inspect the response in the Flow Designer logs.

Note: At the time of testing (Washington through Yokohama releases), Flow Designer encountered difficulties encoding multipart requests correctly. Because of this, we continued with Approach 2, which used scripted logic instead.

---

When to revisit this approach

If Flow Designer adds native support for multipart/form-data requests in a later release, or if your environment requires a no-code integration, this method can provide a cleaner alternative to scripted REST messages.

It also offers stronger visibility and maintainability for administrators who prefer building within Flow Designer rather than custom Script Includes.

---

Summary

This approach was the first attempt to integrate Secured Signing with ServiceNow using Flow Designer and Integration Hub.

While not fully implemented during the proof of concept, it lays the groundwork for future low-code integrations once multipart request handling stabilises across releases.

For the working implementation, see my other article: How to Implement Multipart Upload in ServiceNow for Secured Signing or any APIs requiring this tested and confirmed to function from Washington to Yokohama.