When to Use the HTTP Connector

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 with the Workato SDK provides flexibility for complex triggers and actions, handling pagination, or intricate calls and responses.

HTTP Connector: Ideal for scenarios needing straightforward JSON responses with minimal setup time, making it perfect for quickly calling endpoints.

Use Cases for the HTTP Connector

I’ve used the HTTP connector in various recipes to save time when an out-of-the-box connector wasn’t available. For example:

• Learning Management System: Called endpoints to retrieve enrollee and course data using the same connector, seamlessly passing data between steps.
• Custom API Integration: The development team created an endpoint that the HTTP connector could access, setting up integrations in under 15 minutes compared to a lengthier SDK build-out.

Using the HTTP Connector as a Trigger

Although I typically use the HTTP connector for actions, it also functions as a trigger, similar to a scheduled recipe. It polls the endpoint every 5 minutes, though it doesn’t support pagination, limiting it to the first page of results. For real-time data, consider using a webhook to avoid polling delays.

Authentication Options

Workato’s HTTP connector supports nine authentication types. Refer to your tool's documentation to select the appropriate method:

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