JSON Endpoint Connector

🔌 JSON Endpoint Connector

This connector provides a dedicated webhook URL to ingest JSON payloads from external systems into automation workflows. Every incoming request is validated against a pre-configured body schema and optional custom headers before being forwarded to the runbook.

⚡ Triggers

JSON Endpoint

Fires when an inbound HTTP request is received at the connector's webhook URL. It extracts headers, query parameters, the URL postfix, and the body for use in the workflow.

📥 Input Parameters (Config)

• body_schema (Schema Field, required): Defines the expected JSON structure using a dynamic schema builder.
• headers (List, optional): List of custom HTTP headers to extract, with options to flag them as required or as arrays for comma-separated values.

📤 Output

• body: The parsed JSON body validated against the configured schema.
• query_params: Hash of query parameters extracted from the request URL.
• headers: Extracted header values keyed by header name.
• url_postfix: Optional URL path suffix appended to the webhook URL by the sender.

📌 Use Cases

• Webhook Notifications: Receiving real-time updates from third-party services.
• Form Submissions: Ingesting structured form data into automation workflows.
• External API Requests: Accepting JSON payloads from custom scripts or external applications.

⚠️ Notes

• Authentication: Supports API Key (via header or query param) and HTTP Basic Authentication.
• GET Requests: GET requests are accepted by the endpoint but will produce an empty body value.
• Schema Management: The output schema is regenerated automatically whenever the trigger configuration is updated.
• Special Headers: The x-job-context-identifier header can be used to set the job context but is not included in the output payload.

‍