What problem does it solve? Setting up event-driven reactions in a Weegloo Space requires knowing the exact Webhook resource contract — topic syntax, filter operators, the url-XOR-script rule, transformation templating, and permission constraints. This Skill encodes that contract so an agent can create correct Webhooks without trial-and-error API calls. ## Core Features & Use Cases - Event subscriptions with topics and filters: Subscribe to Content, ContentType, Media, or Comment events (Create, Save, Publish, etc.) with wildcard support and EQ/NE/IN/REGEX filters on sys.id, content type, or editor. - Two mutually exclusive actions: POST a Transformation-shaped request to an external URL with secret headers and Basic auth, or run a Script in the Space that receives the triggering resource as its payload. - Operational guardrails: Covers runAs attribution (HookOwner vs EventUser), the SETTING_WEBHOOK permission requirement, SpaceAccessToken limitations, loop protection, and the Script-deletion block while a Webhook references it. - Use Case: When content is published, notify an external search index by firing a Webhook on Content.Publish filtered to one ContentType, running a Script that POSTs the item and patches an indexedAt field back onto it. ## Quick Start Create a Weegloo Webhook that fires on Content.Publish for a specific ContentType and runs my indexing Script.
