transformations:iteratewebrequest
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
transformations:iteratewebrequest [2021/07/02 21:58] – craigt | transformations:iteratewebrequest [2023/11/02 08:07] (current) – [Options settings] dmitry | ||
---|---|---|---|
Line 13: | Line 13: | ||
\\ | \\ | ||
=====Use cases===== | =====Use cases===== | ||
- | The action is intended for repeating uniform interactions with REST APIs, cloud applications and websites. | + | The action is intended for repeating uniform interactions with REST APIs, cloud applications, and websites. |
\\ | \\ | ||
=====Action settings===== | =====Action settings===== | ||
^ Setting | ^ Setting | ||
- | |Connector< | + | |Connector/Base URL< |
|Request method|Select the request method. | |Request method|Select the request method. | ||
- | |Path< | + | |Path< |
- | |Add URL parameters< | + | |Add URL parameters< |
- | |Body< | + | |Body< |
- | |Headers< | + | |Headers< |
- | |Response< | + | |Response< |
< | < | ||
- | <sup>1</ | + | <sup>%%**%%</ |
\\ | \\ | ||
====Path setting==== | ====Path setting==== | ||
- | The URL path is appended to the endpoint URL specified in the Web Location connector. EasyMorph parameters can be inserted into the path using curly braces if needed. Alternatively, | + | The URL path is appended to the endpoint URL specified in the Web Location connector. EasyMorph parameters can be inserted into the path using curly braces if needed. Alternatively, |
**Examples: | **Examples: | ||
Line 82: | Line 82: | ||
\\ | \\ | ||
__**Form**__\\ | __**Form**__\\ | ||
- | This body type is equivalent to submitting a web-form. Name-value pairs are encoded as if it was a web-form. | + | This body type is equivalent to submitting a web form. Name-value pairs are encoded as if it was a web-form. |
Header Content-Type is automatically set to " | Header Content-Type is automatically set to " | ||
Line 100: | Line 100: | ||
\\ | \\ | ||
__**File**__\\ | __**File**__\\ | ||
- | The request body is read from the specified file and inserted verbatim. | + | The request body is read from the specified file and inserted verbatim. |
+ | |||
\\ | \\ | ||
Line 122: | Line 124: | ||
__**Save response body to file, fail if HTTP error**__\\ | __**Save response body to file, fail if HTTP error**__\\ | ||
In this case, if the response status is not an error (i.e. HTTP status codes 4xx or 5xx) then the response body (only the body!) will be saved verbatim into the specified file (the filename of which can be created automatically, | In this case, if the response status is not an error (i.e. HTTP status codes 4xx or 5xx) then the response body (only the body!) will be saved verbatim into the specified file (the filename of which can be created automatically, | ||
+ | |||
+ | \\ | ||
+ | ====Options settings==== | ||
+ | Check //Send requests in parallel// to enable parallel requests and choose the //Degree of parallelism// | ||
\\ | \\ | ||
Line 135: | Line 141: | ||
When developing workflows with web requests it may be necessary to re-run parts of workflows. In this case, it is recommended to always start from the Web Request actions that do authentication so that the session cookies can be set under the hood. | When developing workflows with web requests it may be necessary to re-run parts of workflows. In this case, it is recommended to always start from the Web Request actions that do authentication so that the session cookies can be set under the hood. | ||
+ | Iterate Web Request automatically sends the // | ||
+ | |||
+ | |||
+ | \\ | ||
+ | =====Community examples===== | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
\\ | \\ |
transformations/iteratewebrequest.txt · Last modified: 2023/11/02 08:07 by dmitry