Overview

Use a 

 to make HTTPS requests to external APIs;

Basic Settings

Expects literal values or expressions encapsulated within ${} syntax, for example ${in.MyValue}.

Input Connection Points

Can Accept a single

.

The grid contains a list of all input connection points and their type.

• To add a new input connection point, in the section toolbar click 

   to open a new input connection point and set its properties; see Input Connection Points.

• To edit an existing input connection point, double-click it in the list to open its properties.

• To remove an input connection point, select one and in the section toolbar click 

  .

Output Connection Points

The grid contains a list of output connection points, by default this will be out and error.

Output Connection Point	Description
Out	Contains the resulting record of the request.
Error	Contains the resulting record of the request where it satisfies the error expression specified on the HTTP Node.

Output Record

An HTTP Node has two output connection points out and error. An HTTP Node is triggered for each input record and will generate one output record which will be sent on either the out or error output. 

The resulting record contains the attributes specified by the output connection point, successful records are passed down the out connection point and records containing an error are passed down the error connection point. The stricture of the records by default is as follows:

1. body: The content returned by a successful request. For example, JSON content.

2. contentType: The type of response provided by the target HTTP request. For example, application/json; charset=utf-8.

3. status: the returned status code. For example, 200.

4. status message: the returns status message. For example, OK.

Connect to a JSON Node or XML Node to the output connection to interpret the response into individual records.

Headers

Are typically used to specify information for the request such as character sets, session tokens or passwords. Headers can make use of the Secret Key Details see below. For more information see HTTP Header. 

For example,

• Name: Content-Type

• Value:  text/xml; charset=UTF-8

Secret Key Details

Secret Keys allow sensitive data such as passwords or security tokens to be encrypted and stored in the PhixFlow Database.

Secret keys have a name which they can be referenced by using the syntax ${_datasource.keyName}. For full details on secret keys see Secret Key and Local Secret.

Description

We recommend that you always enter a description to explain the purpose of this item.

Advanced

Field	Description
Connection Timeout (s)	The maximum time to wait to while attempting to create a connection, measured in seconds. The default for this is set to 300 seconds.
Response Packet Timeout (s)	The maximum time to wait between responses from the data packets, measured in seconds. The default for this is set to 180 seconds.
Prioritise throughput over ordering	When this option is ticked records are processed in parallel to optimise performance. This means the order records are processed is nondeterministic. When unticked (default), records are processed in the order they are provided.