HTTP Request connector

With the HTTP Request connector, you can use commands in a chain to perform hypertext transfer protocol (HTTP) GET, POST, PUT, and DELETE requests to a given URL. For example, you can use this connector in a chain to connect and automate other solutions through their respective connectors.

Note: While the connector has no OData-specific features, you can use a command's Headers or Query string input to include any necessary additional components of a request.

Set up the HTTP Request connector

Note: To make the connector available for use in your organization's chains, an org security administrator first enables it from Configuration.

1. From Chains, click Connections  compare_arrows and Add Connection  add.
2. Under BizApp Connection, select HTTP Request and the default CloudRunner.
   
3. Under Basic Info, enter a unique name and description to help identify the connector.
4. Select the environments to use the connection, and click Save.
5. To test the connection, create and run a chain with the connector's GET command, and verify it returns a valid output. 

Set up optional mTLS authentication

To secure the connector's HTTP requests, you can use mutual Transport Layer Security (mTLS) authentication with its commands.

Note: You can also use basic username/password authentication to secure the connector's requests.

To enable optional mTLS authentication:

1. Provide the Privacy-Enhanced Mail (PEM)-encoded certificates to use with requests:
   • The public/private key pair to send with requests
   • An optional Certificate Authority (CA) certificate

   Note: Workiva does not generate the certificates for HTTP requests.

2. In Chain Builder, upload the certificates as workspace resources.
3. When you set up the connector's command, select the certificates as properties:
   
   
   • For the public/private key pair, select their resources in Certificate and Certificate private key, respectively.
   • For an optional CA certificate, select its resource in CA certificate.