webhook-transforms

Webhook payloads are transformed into markdown pages by mapping raw JSON event data into structured formats with metadata like slugs, types, and citations. This process ensures external event data becomes a consistent, brain-ingestible record for your knowledge base.

Sanitizing untrusted webhook data requires stripping HTML tags and escaping script content to prevent unsafe payloads from entering brain pages. These safety guardrails ensure only clean, secure data is written to your knowledge base.

Dead-letter queues handle failed webhook event transformations by preserving raw payloads and writing failed records to a separate queue while retrying the transform once. This mechanism ensures no data is lost during ingestion failures.

Entity extraction occurs automatically after writing webhook events to brain pages. The workflow extracts entities post-page-creation to ensure the structured signal and citation-backed record are fully established before metadata analysis begins.

Webhook transformation explicitly supports SMS, meeting, and social mention ingestion workflows. Each event type is mapped from raw JSON payloads into a structured brain signal with timeline updates and citation-backed records.

Automating event ingestion requires registering the webhook endpoint, defining the transform mapping, sanitizing the payload, and completing a brain sync step. This pipeline converts external events into structured brain pages with entity extraction and timeline updates.