Skip to content

Connectors & Webhooks

9. Connector Hub

Connector Hub is the integration management panel for connecting Theseus Guard to your existing enterprise security stack. Connectors push governance events to external systems and pull configuration data from organizational systems.

9.1 Connector Grid

All available connectors are displayed as cards in a grid. Each card shows: - Name — The integration name (e.g., "Splunk SIEM", "ServiceNow", "Slack") - Category — The integration type (SIEM, Ticketing, Messaging, Secrets Vault, etc.) - Description — What this connector does - Connection Status — Connected (green) or Disconnected (gray)

9.2 Connector Actions

Each connector card has three action buttons: - Configure — Opens the configuration settings, managed via Policy Studio for most connectors - Test Connection — Sends a test payload to verify the connector endpoint is reachable - Connect / Disconnect — Toggles the connector's active state

9.3 Add Connector

Clicking Add Connector opens a modal to register a custom connector: - Category — Select SIEM, Ticketing, Messaging, Secrets Vault, or Other - Connector URL / Endpoint — The target endpoint URL

Custom connectors are added to the grid and can be configured like built-in connectors.

10. Webhook Routes

Webhook Routes manages outbound webhook subscriptions that fan out Theseus Guard governance events to external systems in real time.

10.1 Routes Table

Each webhook route is shown with: - Name — A descriptive name for the route (e.g., "ServiceNow Integration") - Target URL — The HTTPS endpoint receiving events - Events — The event types subscribed to (comma-separated) - Status — ACTIVE or INACTIVE - Created — Creation date

10.2 Create a Webhook

Clicking Create Webhook opens a modal with: - Name — Route label - Target URL — The destination HTTPS endpoint - Description — Optional description

Event type subscriptions are configured after creation.

10.3 Delivery History

Clicking a webhook route row reveals its Delivery History panel below the table. Each delivery attempt shows: - Event type - Target URL - Status (SENT, FAILED, or PENDING) - HTTP status code returned by the target - Timestamp - Replay button — Retries a failed delivery immediately