webhook-transforms

Webhook payloads are converted into markdown pages by defining a transform function that maps external event schemas to the brain page format, preserving the original payload and metadata citations.

Incoming event data is sanitized during the transform process, and failed events are managed through dead-letter handling to ensure error handling without losing payload provenance or disrupting the brain pipeline.

You register a webhook URL to receive external events, which are then automatically parsed, transformed, and routed through the pipeline to write pages, extract entities, and add timeline entries.

Yes, the framework works across multiple event sources by allowing you to define a specific transform function for each source schema, unifying them into consistent pages with traceable provenance.

After an event is received and transformed, the system writes the page, extracts entities, adds timeline entries, and performs an end-to-end sync to integrate the new data into the pipeline.

Raw external events lack unified formatting because they originate from different schemas. A generic transform framework solves this by mapping payloads to a standard format while preserving citations.