The HTTP node can be used to make HTTP(S) calls from a workflow. This essentially allows you to integrate with any third-party application or service that has an HTTP endpoint. So you can access data from another source, for example, a BitBucket repository; or you can integrate your ticketing system, for example, JIRA, Freshdesk, ServiceNow, Zendesk, etc.
This is an extremely powerful node, that allows extremely complex use cases. To add an HTTP node, click on the ‘+’ and select HTTP. It can be added anywhere in the workflow. Click on the node and select ‘edit’ to open the parameters options for the nodes.
‘Select a resource’ - you can select the relevant Resource ID or Node ID from the dropdown options available. The resource selected can be ‘NONE’ or a specific resource/node attribute.
This will depend on your use case. For example, if you're using the HTTP node to find and filter the instances that have a CPU utilization of less than 10% and then creating a JIRA ticket, you will select the ‘Filter.Instances’ Node ID as the resource. See a usage example of this scenario.
On the contrary, if you’re using the HTTP Node to access a file from your BitBucket repository in the beginning of the workflow, you’re not acting on any particular resource or filter from the workflow, so you’ll set the resource to ‘NONE’.
‘Method’ - There methods that correspond to any valid HTTP request are GET, PUT, POST and DELETE.
GET is used to fetch data from a resource
POST and PUT are for sending data to a server
DELETE is used for deleting the resource
For more details on the basics of what they do click here.
The ‘Endpoint URL’ is obtained from the application that you want to access
The Header, Body and Basic Auth of the node will update based on the Method and the Endpoint URL. Depending on the method selected, you can fill in the Header & Body. Basic Authentication needs to be set to access the file. Here we set the authentication details.