Documentation Workfront Adobe Workfront Fusion

HTTP > Make a request module

Last update: March 14, 2025

Topics:
Workfront Fusion

The Adobe Workfront Fusion HTTP > Make a request module is a universal module that enables you to configure an HTTP request and submit it to a server. The received HTTP response is then contained in the output bundle.

NOTE

If you are connecting to an Adobe product that does not currently have a dedicated connector, we recommend using the Adobe Authenticator module.

For more information, see Adobe Authenticator module.

Access requirements

Expand to view access requirements for the functionality in this article.

You must have the following access to use the functionality in this article:

Adobe Workfront package	Any
Adobe Workfront license	New: Standard Or Current: Work or higher
Adobe Workfront Fusion license**	No Workfront Fusion license requirement
Product	New: Select or Prime Workfront package: Your organization must purchase Adobe Workfront Fusion. Ultimate Workfront package: Workfront Fusion is included. Or Current: Your organization must purchase Adobe Workfront Fusion.

For more detail about the information in this table, see Access requirements in documentation.

For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.

HTTP > Make a request module configuration

When you configure the HTTP > Make a request module, Adobe Workfront Fusion displays the fields listed below. A bolded title in a module indicates a required field.

Evaluate all states as errors (except for 2xx and 3xx)	Use this option to set up error handling. For more information, see Add error handling.
URL	Enter the URL you want to send a request to, such as an API endpoint, or website.
Method	Select the HTTP request method you need to configure the API call. For more information, see HTTP request methods.
Headers	Add the headers of the request in the form of a standard JSON object. For example, `{"Content-type":"application/json"}`
Query String	Enter the desired query key-value pairs.
Body type	The HTTP Body is the data bytes transmitted in an HTTP transaction message immediately following the headers if there are any to be used. Raw The Raw body type is generally suitable for most HTTP body requests even in situations where developer documentation does not specify data to send. Specify a form of parsing the data in the Content type field. Despite the content type selected, data is entered in any format that is stipulated or required by the developer documentation. Application/x-www-form-urlencoded This body type is to POST data using `application/x-www-form-urlencoded`. For `application/x-www-form-urlencoded`, the body of the HTTP message sent to the server is essentially one query string. The keys and values are encoded in key-value pairs separated by `&` and with a `=` between the key and the value. For binary data, use `multipart/form-data` instead. Example: Example of the resulting HTTP request format: `field1=value1&field2=value2` Multipart/form-data The Multipart/form-data is an HTTP multipart request used to send files and data. It is commonly used to upload files to the server. Add fields to be sent in the request. Each field must contain Key-Value pair. Text Enter the key and value to be sent within the request body. File Enter the key and specify the source file you want to send in the request body. Map the file you want to upload from the previous module (such as HTTP > Get a File or Google Drive > Download a File), or enter the file name and file data manually.
Parse response	Enable this option to automatically parse responses and convert JSON and XML responses. Before you can use parsed JSON or XML content, run the module once manually so that the module can recognize the response content and allow you to map it in subsequent modules.
User name	Enter the user name if you want to send a request using basic authorization.
Password	Enter the password if you want to send a request using basic authorization.
Timeout	Specify the request timeout in seconds (1-300). The default is 40 seconds.
Share cookies with other HTTP modules	Enable this option to share cookies from the server with all HTTP modules in your scenario.
Self-signed certificate	To add a self-signed certificate: Click Extract. Select the type of file you are extracting. Select the file that contains the or certificate. Enter the password for the file. Click Save to extract the file and return to the module setup.
Reject connections that are using unverified (self-signed) certificates	Enable this option to reject connections that are using unverified TLS certificates.
Follow redirect	Enable this option to follow the URL redirects with 3xx responses.
Follow all redirects	Enable this option to follow the URL redirects with all response codes.
Disable serialization of multiple same query string keys as arrays	By default, Workfront Fusion handles multiple values for the same URL query string parameter key as arrays. For example, `www.test.com?foo=bar&foo=baz` will be converted to `www.test.com?foo[0]=bar&foo[1]=baz`. Activate this option to disable this feature.
Request compressed content	Enable this option to request a compressed version of the website. Adds an `Accept-Encoding` header to request compressed content.
Use Mutual TLS	Enable this option to use Mutual TLS in the HTTP request. For more information on Mutual TLS, see Use Mutual TLS in HTTP modules.

recommendation-more-help

Example: This example shows how to set up the module to submit a POST request with JSON payload:

Make a request example

We do not recommend mixing JSON pieces with expressions and items directly in the Request content field, because it can result in invalid JSON.