HTTP

Webhooks in Quickwork can use universal connectors like HTTP and WebSockets to generate endpoints. These endpoints can receive traffic and payloads from any source system, including third-party or custom-designed software applications. Webhooks follow a "fire and forget" mechanism, meaning they do not wait for a reply from the journey. Quickwork acknowledges each request sent to the webhook with a 200 status code and a message body stating OK. This system supports payloads up to 10 MB, or even larger if octet streaming is used. Although webhooks also have a 90-second timeout, they typically respond within 100 milliseconds as no response is expected from the API.

What is HTTP app on Quickwork

HTTP app on Quickwork allows you to receive calls from external systems and set up a webhook URL to consume events from external services. For instance, it can handle new order events from an e-commerce platform that supports webhooks. The HTTP app can accept webhook events when a specific app's connector is not yet available on Quickwork. Additionally, HTTP actions allow you to make API calls to external systems, serving as a versatile alternative when a dedicated API for a service is not supported by Quickwork.

Key components of HTTP app

1. Request URL: The endpoint to which the HTTP request is sent.
2. HTTP method: Defines the type of request, GET, POST, PUT, PATCH, or DELETE.
3. Request headers: Key–value pairs used to include metadata like authentication tokens, content type, or API keys.
4. Request body: The payload or data sent with the request, typically in JSON, XML, or form-data format.
5. Query parameters: Used to append dynamic values to the URL for filtering, sorting, or fetching specific records.
6. Response body: The data returned by the external API, which can be parsed and used as data pills in subsequent steps.
7. Response status code: Indicates the result of the request (for example, 200 OK, 400 Bad Request, 401 Unauthorized).
8. Content type: Defines the format of data being sent or received, such as application/json or text/plain.

Why is HTTP app essential in automation

HTTP enables the integration and interaction of different systems, particularly in scenarios where direct triggers or actions are unavailable on platforms like Quickwork. By using the HTTP app, you can:

• Create custom integrations (triggers and actions) by making HTTP calls to external applications' APIs.
• Set up webhooks to receive real-time data from other services, especially for applications without native event support. Webhooks use HTTP to send data to other platforms, enabling dynamic information exchange between systems.
• When a specific application does not have a ready-made trigger or action within Quickwork, HTTP can bridge that gap. You can configure HTTP requests to interact directly with the application's API, allowing seamless data transmission and actions.

Benefits of HTTP app in automation

• Flexibility: Offers the flexibility to connect with any external system that supports HTTP, expanding the range of possible integrations.
• Real-time data handling: Enables real-time data exchange and processing, making it indispensable for time-sensitive operations.
• Customization: Allows you to create highly customized solutions tailored to specific business needs.

📚 Additional resources

Using HTTP as a trigger
Using HTTP as an action