webhook-transforms

Webhook event processing involves ingesting external payloads, sanitizing inputs to prevent XSS, extracting entities, and writing structured pages with citations. This skill automates that deterministic transform pipeline for immediate brain ingestion.

Sanitizing incoming payloads requires removing HTML and script tags to prevent XSS while preserving raw payload structure for traceability. This skill applies data sanitization automatically before writing brain pages.

Yes, processing SMS and social mentions through a single webhook endpoint is possible by registering transforms that handle multiple event types. This skill orchestrates incoming events from various external services into standardized brain pages.

Entity extraction during event processing automatically derives entities from sanitized input and links them to related brain pages. This enables timeline integration and enriches ingested data without manual tagging.

If a webhook transform fails during brain ingestion, the errored event is routed to a dead-letter queue. This prevents data loss and allows you to retry or inspect the failed payload later for troubleshooting.

Yes, preserving raw webhook payloads after conversion is necessary for traceability. The skill retains original unstructured data alongside structured brain pages, allowing you to audit transformations and verify entity extraction accuracy.