Agent skill · software engineering · jeremylongshore
framer-webhooks-events
Implement Framer webhook signature validation and event handling.
Why this skill is useful
Provides specific implementation patterns for Framer webhook signature validation and event handling that the AI wouldn't reliably generate on its own.
What it needs
Requires express, framer-api installed locally. Requires framer account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Framer Webhooks & Events Prerequisites Approved event source/destinations, signing or authentication controls where supported, event ledger, redaction policy, and synthetic fixtures. Error Handling Reject unknown event schemas/destinations, deduplicate replayed events, bound retries, and pause downstream actions on access or privacy failures. Examples Deliver a fictional event twice, process it once under an opaque ID, and reject an unknown destination without forwarding page or visitor data. Overview Framer's Server API uses a WebSocket channel for real-time communication, not traditional REST webhooks. For event-driven integrations, you subscribe to changes via the WebSocket connection or set up your own webhook endpoints that trigger Framer sync via the Server API. Instructions Step 1: Subscribe to CMS Changes via Server API Step 2: External Webhook → Framer Sync Step 3: Plugin Event Subscriptions Output WebSocket-based real-time CMS subscriptions External webhook handler triggering Framer sync Plugin event subscriptions for canvas changes Resources Framer Server API Plugin Subscriptions Next Steps For performance, see framer-performance-tuning.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/framer-webhooks-events--aba767