framer-webhooks-events

Implement Framer webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling Framer event notifications securely. Trigger with phrases like "framer webhook", "framer events", "framer webhook signature", "handle framer events", "framer notifications".

Allowed Tools

ReadWriteEditBash(curl:*)

Provided by Plugin

framer-pack

Claude Code skill pack for Framer (18 skills)

saas packs v1.5.0
View Plugin

Installation

This skill is included in the framer-pack plugin:

/plugin install framer-pack@claude-code-plugins-plus

Click to copy

Instructions

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


import { framer } from 'framer-api';

async function watchChanges() {
  const client = await framer.connect({
    apiKey: process.env.FRAMER_API_KEY!,
    siteId: process.env.FRAMER_SITE_ID!,
  });

  // Subscribe to collection changes
  const collections = await client.getCollections();
  for (const col of collections) {
    col.subscribe((items) => {
      console.log(`Collection "${col.name}" updated: ${items.length} items`);
    });
  }
}

Step 2: External Webhook → Framer Sync


// Receive webhook from your CMS, sync to Framer
import express from 'express';
import { framer } from 'framer-api';

const app = express();
app.use(express.json());

app.post('/webhooks/cms-update', async (req, res) => {
  const { event, data } = req.body;

  // Validate webhook source
  const signature = req.headers['x-webhook-signature'];
  if (!verifySignature(req.body, signature as string)) {
    return res.status(401).json({ error: 'Invalid signature' });
  }

  if (event === 'content.updated') {
    const client = await framer.connect({
      apiKey: process.env.FRAMER_API_KEY!,
      siteId: process.env.FRAMER_SITE_ID!,
    });

    const col = (await client.getCollections()).find(c => c.name === data.collection);
    if (col) {
      await col.setItems(data.items.map(i => ({ fieldData: i })));
      await client.publish();
      console.log(`Synced ${data.items.length} items and published`);
    }
  }

  res.json({ received: true });
});

Step 3: Plugin Event Subscriptions


// Inside a Framer plugin — subscribe to canvas changes
import { framer } from 'framer-plugin';

// Watch for selection changes
framer.subscribeToSelection((selection) => {
  console.log('Selection changed:', selection.length, 'layers');
});

// Watch for code file changes
framer.subscribeToCodeFiles((codeFiles) => {
  console.log('Code files updated:', codeFiles.map(f => f.name));
});

Output

  • WebSocket-based real-time CMS subscriptions
  • External webhook handler triggering Framer sync
  • Plugin event subscriptions for canvas changes

Resources

Next Steps

For performance, see framer-performance-tuning.

Ready to use framer-pack?