webhook-transforms

Convert external webhook events into brain-ingestible pages with entity extraction.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill webhook-transforms-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-transforms
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/webhook-transforms
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill webhook-transforms-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? External events like SMS messages, meeting completions, and social mentions arrive as raw JSON payloads that cannot be directly stored or searched in a knowledge base. This Skill provides a framework for transforming those payloads into structured brain pages with citations, entity extraction, and timeline entries. ## Core Features & Use Cases - Transform Framework: Define a transform function that maps raw webhook JSON payloads to brain page markdown with metadata (slug, type, citations). - Input Sanitization: Strips HTML tags and escapes script content before writing to the brain, preventing XSS risks. - Dead-Letter Queue: Failed transforms log the raw payload to _dead-letter/{timestamp}.md and retry once, so no events are silently lost. - Use Case: Connect an SMS provider's webhook so that every incoming text message automatically becomes a timeline entry on the sender's brain page, with action items detected and entities enriched. ## Quick Start Set up a webhook transform that converts incoming SMS events into brain timeline entries with entity extraction.

Frequently Asked Questions about webhook-transforms

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

FAQPage Schema
How do I transform webhook payloads into knowledge base pages?

Define a transform function that maps the raw JSON payload to brain page markdown with metadata like slug, type, and citations. Register the webhook URL with the external service, and each incoming event is parsed, transformed, and written via gbrain put.

How to handle failed webhook event processing without losing data?

Failed transforms log the raw payload to a dead-letter queue at _dead-letter/{timestamp}.md and retry once. The error type is surfaced to the agent, so events are never silently dropped.

What event types can webhook transforms process?

The framework handles SMS received events, meeting completions (delegated to the meeting-ingestion skill), and social mentions from platforms like Twitter. Each event type maps to a specific brain output such as timeline entries or media pages.

Does webhook ingestion sanitize external input before storage?

Yes, all transforms must strip HTML tags and escape script content before writing brain pages. This prevents XSS risks from untrusted external payloads entering the knowledge base.

What are the limitations of webhook-based event ingestion?

Transforms depend on a correctly defined mapping for each event schema, so unknown payload shapes will fail into the dead-letter queue. Entity extraction and enrichment also require the gbrain pipeline to be running and synced.