1. Home
  2. Knowledge Base
  3. Setting up Workflows
  4. The Basics of HTTP Workflow nodes

The Basics of HTTP Workflow nodes

In this article, we’ll be covering the fundamentals of HTTP Workflow nodes.

HTTP Workflow Nodes Explained

There are three request methods that can be used PUTPOST, and GET. Here are some examples of how you might use each request method: 

  • You may use a POST request when pushing data for reporting to an external system
  • POST request may be used if you are updating or actioning something in an external system
  • GET requests, may be used when retrieving information from an external application and then using or displaying this in Gnatta.

The URL field is where you send the request from workflow. 


The Content Type can be set to either “text/plain” or “json/application” on PUT and POST methods.


The Body field is where the payload of the request is added; see our property list for available options. 


There are three possible Modes to chose once a node fails:  

  • Fail on error: the workflow throws an error; the remaining workflows, and proceeding workflows, on that trigger for the action will not run.  
  • Continue on error: despite the error, the proceeding workflow and other workflows will run on the trigger for that specific action. 
  • Handle Error: when an error is thrown, a decision can then be made whether to direct the call elsewhere or process the remaining workflow differently.  

Context Output is customisable, allowing you to define the response context. This allows you to reference the response information in a later Node or Workflow.  

OAuth Credentials can be used to authenticate a request. If a signing key is configured, then this will be used instead to provide a signed request.

🔍Check out next

Was this article helpful?

Need Support?

Can't find the answer you're looking for?
Contact Support