HTTP node can be used to make HTTP(S) calls from a workflow. The HTTP node has several abilities that help one integrate to tools like calling an API endpoint or a ticketing system such as JIRA, Freshdesk to name a few. This can also be used to trigger one of Totalcloud's workflows. You can add new collections, update existing collections, override existing databases, or delete the database directly through this node. Predominantly any software system that has a HTTP end point can be triggered through this node.
An API request lets you contact a server with API endpoints that you want to reach and perform some action. Those actions are HTTP methods. If you are using APIs to build client-side applications - mobile apps, websites or desktop applications - you might want to see the actual HTTP request traffic that is being sent and received in the application.
Lets look at all the parts of a HTTP node:
Each node in workflow can refer to the output of any other node in a workflow that was executed before it. lets say in a workflow A->B->C->D , C can refer to B’s output and A’s output, similarly D can refer to A,B, and C’s output as it’s input. We select this using “Select Input Collection”
There are various methods that correspond to any valid HTTP request method. One can capture the HTTP requests using the following: GET, PUT, POST, DELETE. As the name suggests the GET method lets you fetch data from a specified resource, the POST method lets you extract data from a specified resource and so on with the PUT and DELETE methods. For more details on the basics of what they do click here.
An Endpoint URL is the final location where you want all the work done to reflect.
For a usage example click here.