Networking automation templates

Three HTTP calls, one node. A plain read of a public exchange rate service, the same call behind a password, and a call that carries a file. They differ only in their properties, which is the point: authentication is a property and not a different node, and neither is a multipart body. Basic Authentication takes a vault item and nothing else, so no password is written into the flow, and an at-sign in front of a path is what makes the node open that file and send it as a form part, exactly the way curl does it.

A flow that waits to be called. Http In gives it a public URL that Robomotion hosts for you, with no port to open and no tunnel to run, and Http Out answers on the same held-open request. Between the two, the robot does what a web service cannot do for itself: it opens a real browser, loads the page it was asked about, waits three seconds for it to settle, and photographs it. The reply is the PNG, attached to the response, so curl -o shot.png is a complete client and nothing about the caller needs to know what Robomotion is.

Creates a simple REST API server with GET and POST endpoints using the Net Http nodes. The default robot runs on http://localhost:9090.

Sends an HTTP GET request to a sample service and displays the response in a message box. Defaults to querying https://ifconfig.me for your public IP address.