Featured image for blog post on when to use the Workato HTTP Connectior

When To Use The HTTP Connector

ByJason Raisleger

Workato provides a range of connectivity options, making recipe building seamless. The platform offers native connectors for popular tools and an SDK for creating custom connectors. Additionally, the HTTP connector is available for quick integration within recipes.

HTTP Connector vs SDK: Choosing the Right Approach

SDK: Building a connector using the Workato SDK offers greater flexibility and granularity. This option is suitable for handling triggers and actions that require pagination or complex calls and responses.

HTTP Connector: Ideal for scenarios where a straightforward JSON response is sufficient. It requires minimal setup time, making it perfect for calling endpoints quickly.

When I Use the HTTP Connector

I have used the HTTP connector in a few recipes to save time where an out of the box connector wasn’t available. In one instance, we had a learning management system where I needed to call an endpoint to get enrollee information and course information. I was able to use the same connector for both steps and pass the enrollee information from step 1 to the course information in step 2.

In another instance, our dev team created an endpoint that we used in one of our recipes. It would have been very time consuming to build out a connector using the SDK but using the HTTP actions got us up and running in under 15 minutes.

Use the HTTP Connector as a Trigger

I have only used the HTTP connector as an action but you can use it as a trigger as well. It works much like a scheduled recipe and it will poll the endpoint every 5 minutes. As mentioned above, it will not work with pagination so you will only get the first page of results. Alternatively, you can use a webhook to get events as they happen and that way you don’t need to poll and endpoint to get responses.

Authentication

Workato offers nine authentication options. Refer to the documentation of the specific tool to determine the applicable authentication method:

  • None
  • Basic
  • Head
  • Query Parameters
  • OAuth 2 (authorization code grant)
  • OAuth 2 (client credentials grant)
  • AWS IAM Role Auth
  • AWS Access Key Auth
  • Custom

Similar Posts

Workato Naming Convention Best Practices

Workato Naming Convention Best Practices

ByJason Raisleger

Maintaining a standard naming convention in Workato is a key factor in ensuring an organized workspace and easy asset retrieval. Although each Workato instance may have unique characteristics, establishing rules and adhering to general best practices in naming conventions is a solid starting point that can be customized as needed. Naming Convention Example [MK]-MITF-FCT-03 >…

Using Marketo Flow Step Service with Workato

Using Marketo Flow Step Service with Workato

ByJason Raisleger

The introduction of Self Service Flow Steps in the August 2022 Marketo release caught my attention, but it wasn’t until midway through last year that I delved deep into exploring how I could leverage this feature in conjunction with Workato. As I explored its capabilities, it quickly became evident just how potent this new functionality…

Persistent Variables in Workato with a Global Variables Lookup Table

Persistent Variables in Workato with a Global Variables Lookup Table

ByJason Raisleger

When building  Workato recipes, there often arises a need for variables that persist across different jobs. Unfortunately, the native Variables action step falls short in this regard, as it resets with each job iteration. In this blog post, I’ll share a workaround I devised to overcome this limitation by leveraging a Global Variables Lookup Table….