Custom Actions

Prev Next

The Custom action feature enables you to create and execute an HTTP request using your OneSpan Sign connection.

This action can be used to access any OneSpan Sign API endpoint that is not included in the prebuilt actions. The request will be automatically authorized with your OneSpan Sign connection, so you only need to specify the HTTP details.

For a list of available endpoints and payload structures, refer to the OneSpan Sign API documentation.

Input fields

Input field

Description

Action name

Assign a descriptive name to this custom action, such as Generate Signing URL or Send Transaction.

Path

This is the path that will be added to the base URI of your OneSpan Sign connection (for example, if your base URI is https://sandbox.esignlive.com/, a sample path could be /api/packages). You can also provide an absolute URI to override the base URI.

Method

Select the HTTP method for the request: GET, POST, PUT, or DELETE.

Request type

Available for POST/PUT/DELETE. Choose the format for sending data in the request: JSON, Raw JSON, Multipart form, or Plain text.

Input

Available for POST/PUT/DELETE. Construct your request payload based on the Request type you selected (for instance, define the fields in the JSON body).

Available for GET. Set up query parameters to be added to the request URL.

Request headers

Include any headers required by the OneSpan Sign API, such as "Content-Type: application/json" or other custom headers.

Response type

Select how the response should be processed. Use JSON response if you want to extract output fields from a JSON body.

Response body

This is available when JSON response is selected. Specify the expected fields from the JSON response so they can be used as output fields.

Response headers

Optionally define the structure of any headers returned in the response if you wish to use them later.

Output fields

The output fields are determined by your Response body configuration. When the Response type is set to JSON, Workato will parse the response according to the Response body definition and make those fields available as structured outputs for use in your recipe.