transformations:webrequest
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
transformations:webrequest [2019/10/31 08:05] – [Request headers] dmitry | transformations:webrequest [2019/10/31 08:08] – [Web Request] dmitry | ||
---|---|---|---|
Line 3: | Line 3: | ||
Category: Workflow / External | Category: Workflow / External | ||
- | Sends an HTTP request to a web server and receives a response. Intended for interactions with REST APIs, cloud applications and websites. Requires a configured Web Location connector. | + | Sends a single |
Supports all HTTP methods - GET, POST, PUT, DELETE, HEAD, OPTIONS, CONNECT, TRACE, PATCH. | Supports all HTTP methods - GET, POST, PUT, DELETE, HEAD, OPTIONS, CONNECT, TRACE, PATCH. | ||
Line 24: | Line 24: | ||
| %%https:// | | %%https:// | ||
+ | If a Web Location connector has permanent URL parameters specified they will be appended to all requests that are made using the connector. This can be used for scenarios where all requests should have an API key or secret specified. | ||
====Request body==== | ====Request body==== | ||
The request body can be specified in one of the following ways: | The request body can be specified in one of the following ways: | ||
Line 100: | Line 101: | ||
When project execution is finished, the cookie container is discarded. No cookies are stored in project or Web Location connector. | When project execution is finished, the cookie container is discarded. No cookies are stored in project or Web Location connector. | ||
+ | |||
+ | ====See also==== | ||
+ | |||
+ | * [[transformations: |
transformations/webrequest.txt · Last modified: 2023/04/21 03:52 by dmitry