Webhooks

Webhooks allow external systems -- monitoring platforms, CI/CD pipelines, ticketing systems, or any HTTP-capable service -- to send structured events into GNETiX. Each event is processed by the Director just like a chat message, enabling AI-powered responses to infrastructure events.

How It Works

1. You create a webhook endpoint in the GNETiX portal
2. GNETiX generates a unique URL and signing secret
3. You configure your external system to POST JSON payloads to that URL
4. GNETiX verifies the HMAC signature, processes the event through the Director, and optionally notifies users on chat platforms

Setup

Step

Create a Webhook Endpoint

1. Navigate to Webhooks in the GNETiX portal
2. Click Create Webhook
3. Give it a name and optional description
4. Optionally assign an agent to handle events from this webhook
5. Optionally add custom instructions that are injected into the Director's context when processing events from this webhook
6. Click Create

Step

Copy the URL and Secret

After creation, GNETiX displays the webhook URL and signing secret. Copy both values.

Step

Configure Your External System

Point your external system's webhook configuration at the GNETiX URL. Include the HMAC signature in the request header for verification (see below).

HMAC Signature Verification

GNETiX verifies the authenticity of incoming webhook payloads using HMAC-SHA256. The external system must include a signature header computed from the raw request body and the signing secret.

X-Webhook-Signature: sha256=<hex-digest>

The signature is computed as:

import hmac, hashlib

signature = hmac.new(
    secret.encode(),
    request_body,
    hashlib.sha256
).hexdigest()

Requests with missing or invalid signatures are rejected with a 401 status.

Features

Custom Instructions

Each webhook can have custom instructions that are prepended to the Director's system prompt when processing events from that webhook. This lets you tailor the AI's behavior per source system. For example:

"You are receiving alerts from Dynatrace. Summarize the problem, identify the affected service, and suggest remediation steps."

Agent Assignment

Assign a specific agent to a webhook so that events from that source are always routed to the appropriate on-prem tool executor. This is useful when different monitoring systems map to different infrastructure domains.

IP Allowlisting

Restrict which IP addresses can send events to a webhook endpoint. Only requests from allowed IPs will be accepted. This adds an additional layer of security on top of HMAC verification.

Deduplication

GNETiX deduplicates webhook events based on a hash of the request body. If the same payload is received multiple times within a configurable window, duplicate events are silently dropped.

Notify Platforms

After the Director processes a webhook event, the response can be forwarded to one or more users on Webex, Slack, or Teams. Configure notify targets on the webhook to automatically push AI-generated summaries to the right people.

Event History

Every webhook event is logged with its payload, processing status, and Director response. View the event history from the webhook detail page in the portal. Events are also available via SSE streaming for real-time monitoring.

Secret Rotation

To rotate a webhook signing secret:

1. Go to the webhook detail page
2. Click Rotate Secret
3. Copy the new secret and update your external system
4. The old secret is immediately invalidated