webhook-transforms

Convert external event payloads into brain pages with citations via webhooks.

Updated May 16, 2026

Search Tags:#webhook #error-handling #transform #entity-extraction #data-sanitization #brain-pages

Ready to run

npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill webhook-transforms-morris-utrust

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: webhook-transforms
Source: https://github.com/Morris-UTRUST/GBrain-knowledge/tree/main/skills/webhook-transforms
Command: npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill webhook-transforms-morris-utrust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External events are difficult to unify into brain pages with consistent formatting and traceable provenance. This Skill provides a generic framework to convert raw event payloads into brain-ingestible signals, preserving payloads and citations, while ensuring sanitization and error handling.

Core Features & Use Cases

Define transform function mapping external event schemas to brain page format (markdown) and metadata
Register a webhook URL to receive events and route through the brain pipeline
On event received: parse payload, run transform, write brain page, extract entities, add timeline entries, and sync

Quick Start

Frequently Asked Questions about webhook-transforms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert external webhook payloads into formatted markdown pages?▼

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.

What is the best way to handle webhook error handling and sanitize incoming event data?▼

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.

How do I register a webhook URL to route external events through a data 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.

Does this webhook transform approach work across multiple event sources?▼

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.

What happens after an event is received and transformed by the webhook?▼

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.

Why do my external event payloads lack consistent formatting and traceable provenance?▼

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.