HTTP Connector

🔌 HTTP Connector

This connector provides a versatile tool for interacting with APIs that do not have a dedicated, named connector. It gives the user full control over the request structure, including the method, path, headers, and body.

⚡ Actions

Send HTTP request

Sends a custom HTTP request to an external application.

📥 Input Parameters

• method (String, Required): The HTTP verb to use, such as GET, POST, PUT, PATCH, or DELETE.
• path (String, Optional): The URL path appended to the connection's base URL.
• headers (Array, Optional): A list of key-value pairs sent as HTTP request headers.
• query_parameters (Array, Optional): Key-value pairs appended to the URL as query string parameters.
• body (Binary, Optional): The raw request body content.

📤 Output

• response.status (Integer): The HTTP status code returned by the server (e.g., 200, 404, 500).
• response.headers (Array): The response headers as name-value pairs.
• response.body (Binary): The raw response body content.

📌 Use Cases

• Fetching Data: Retrieving information from third-party REST APIs.
• Webhooks: Posting payloads to external webhooks or callback URLs.
• Internal Services: Integrating with internal microservices over HTTPS.
• Generic Integration: Calling any API that lacks a dedicated connector.

⚠️ Notes

• Authentication: Supports API Key, Basic Auth, Bearer Token, and OAuth 2.0.
• Error Handling: HTTP 4xx and 5xx error responses are returned as-is in the output for downstream handling in the runbook rather than failing the job automatically.
• Binary Body: The request body is sent as raw binary; you must set the Content-Type header explicitly if required by the target API.

‍