Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Excerpt | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
OverviewUse a
Basic SettingsExpects literal values or expressions encapsulated within ${} syntax, for example
Input Connection PointsCan Accept a single
The grid contains a list of all input connection points and their type.
Output Connection PointsThe grid contains a list of output connection points, by default this will be out and error.
Output RecordAn HTTP Node has two output connection points The resulting record contains the attributes specified by the output connection point, successful records are passed down the body: The content returned by a successful request. For example, JSON content. : The type of response provided by the target HTTP request. For example,application/json; charset=utf-8 .status: the returned status code. For example, status message: the returns status message. For example,
HeadersAre 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,
See HTTP Action Configuration for an example. Secret Key DetailsSecret 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 HTML Comment | | true |
Tip |
---|
Care should be taken if setting an automatic retry in response to a timeout as it may not always be appropriate, e.g. if the URL HTTP action causes a job to be started on a target system, receiving a timeout does not mean that the job was not started and , therefore retrying (and possibly starting multiple processes or updates on a target system) might be the wrong solution). upport retrying operations in the following scenarios: A transmission error / timeout occurs Specific status codes are returned . |
Expressions can use _result to access the last response and tracking information. The initial requests will get a partially populated _result record. Using _result allows the action to modify the request, such as to follow redirects or links, or submit a token returned by the previous request.
Field | Description |
---|---|
Retry Expression | The default is false. Enter an expression that when it evaluates to true, the connection will be reattempted, instead of continuing through the Actionflow. |
When a Retry Expression is entered, the following options are available: | |
Retry Interval Expression (ms) | The default value is 1000. Enter an expression that when it evaluates to an integer, it determines the amount of time between attempted requests. |
Maximum Retries | The default value is 3. This is the maximum number of times the HTTP action will try the HTTP connection before continuing. This must be an integer between 1 and 60. |
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. |
More Options > Run Action
Individual
action nodes can be run in isolation from the rest of the Actionflow, using the Insert excerpt _http _http nopanel true
option, found under the Insert excerpt _run_action _run_action nopanel true
menu on the HTTP action's Properties. See Running Actions and Actionflows. Insert excerpt _more_options _more_options nopanel true