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 11:17] – [Cookies] dmitry | transformations:webrequest [2020/11/28 06:08] – [Web Request] dmitry | ||
---|---|---|---|
Line 3: | Line 3: | ||
Category: Workflow / External | Category: Workflow / External | ||
- | Sends a single 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 HTTP request to a web server and receives a response. Intended for interactions with REST APIs, cloud applications and websites. Requires a configured |
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 104: | Line 104: | ||
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. | ||
- | ====See also==== | + | ** See also ** |
- | * [[transformations: | + | |
+ | * [[connectors: |
transformations/webrequest.txt · Last modified: 2023/04/21 03:52 by dmitry