windsurf-webhooks-events
Implement Windsurf webhook signature validation and event handling.Use when setting up webhook endpoints, implementing signature verification,or handling Windsurf event notifications securely.Trigger with phrases like "windsurf webhook", "windsurf events","windsurf webhook signature", "handle windsurf events", "windsurf notifications".
When & Why to Use This Skill
The Windsurf Webhooks & Events skill provides a comprehensive framework for developers to securely implement and manage Windsurf webhook integrations. It simplifies the complex tasks of HMAC SHA256 signature validation, replay attack protection, and idempotent event processing, ensuring that your application handles real-time notifications from Windsurf with enterprise-grade security and reliability.
Use Cases
- Setting up a secure Express.js endpoint to receive and process real-time resource notifications from Windsurf.
- Implementing cryptographic signature verification to prevent unauthorized or spoofed webhook requests.
- Protecting against replay attacks by validating webhook timestamps and ensuring request freshness.
- Building robust event-driven workflows using a structured handler pattern for different Windsurf event types.
- Ensuring data consistency by implementing idempotency checks with Redis to prevent duplicate processing of the same event.
| name | windsurf-webhooks-events |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(curl:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Windsurf Webhooks & Events
Overview
Securely handle Windsurf webhooks with signature validation and replay protection.
Prerequisites
- Windsurf webhook secret configured
- HTTPS endpoint accessible from internet
- Understanding of cryptographic signatures
- Redis or database for idempotency (optional)
Webhook Endpoint Setup
Express.js
import express from 'express';
import crypto from 'crypto';
const app = express();
// IMPORTANT: Raw body needed for signature verification
app.post('/webhooks/windsurf',
express.raw({ type: 'application/json' }),
async (req, res) => {
const signature = req.headers['x-windsurf-signature'] as string;
const timestamp = req.headers['x-windsurf-timestamp'] as string;
if (!verifyWindsurfSignature(req.body, signature, timestamp)) {
return res.status(401).json({ error: 'Invalid signature' });
}
const event = JSON.parse(req.body.toString());
await handleWindsurfEvent(event);
res.status(200).json({ received: true });
}
);
Signature Verification
function verifyWindsurfSignature(
payload: Buffer,
signature: string,
timestamp: string
): boolean {
const secret = process.env.WINDSURF_WEBHOOK_SECRET!;
// Reject old timestamps (replay attack protection)
const timestampAge = Date.now() - parseInt(timestamp) * 1000;
if (timestampAge > 300000) { // 5 minutes
console.error('Webhook timestamp too old');
return false;
}
// Compute expected signature
const signedPayload = `${timestamp}.${payload.toString()}`;
const expectedSignature = crypto
.createHmac('sha256', secret)
.update(signedPayload)
.digest('hex');
// Timing-safe comparison
return crypto.timingSafeEqual(
Buffer.from(signature),
Buffer.from(expectedSignature)
);
}
Event Handler Pattern
type WindsurfEventType = 'resource.created' | 'resource.updated' | 'resource.deleted';
interface WindsurfEvent {
id: string;
type: WindsurfEventType;
data: Record<string, any>;
created: string;
}
const eventHandlers: Record<WindsurfEventType, (data: any) => Promise<void>> = {
'resource.created': async (data) => { /* handle */ },
'resource.updated': async (data) => { /* handle */ },
'resource.deleted': async (data) => { /* handle */ }
};
async function handleWindsurfEvent(event: WindsurfEvent): Promise<void> {
const handler = eventHandlers[event.type];
if (!handler) {
console.log(`Unhandled event type: ${event.type}`);
return;
}
try {
await handler(event.data);
console.log(`Processed ${event.type}: ${event.id}`);
} catch (error) {
console.error(`Failed to process ${event.type}: ${event.id}`, error);
throw error; // Rethrow to trigger retry
}
}
Idempotency Handling
import { Redis } from 'ioredis';
const redis = new Redis(process.env.REDIS_URL);
async function isEventProcessed(eventId: string): Promise<boolean> {
const key = `windsurf:event:${eventId}`;
const exists = await redis.exists(key);
return exists === 1;
}
async function markEventProcessed(eventId: string): Promise<void> {
const key = `windsurf:event:${eventId}`;
await redis.set(key, '1', 'EX', 86400 * 7); // 7 days TTL
}
Webhook Testing
# Use Windsurf CLI to send test events
windsurf webhooks trigger resource.created --url http://localhost:3000/webhooks/windsurf
# Or use webhook.site for debugging
curl -X POST https://webhook.site/your-uuid \
-H "Content-Type: application/json" \
-d '{"type": "resource.created", "data": {}}'
Instructions
Step 1: Register Webhook Endpoint
Configure your webhook URL in the Windsurf dashboard.
Step 2: Implement Signature Verification
Use the signature verification code to validate incoming webhooks.
Step 3: Handle Events
Implement handlers for each event type your application needs.
Step 4: Add Idempotency
Prevent duplicate processing with event ID tracking.
Output
- Secure webhook endpoint
- Signature validation enabled
- Event handlers implemented
- Replay attack protection active
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Invalid signature | Wrong secret | Verify webhook secret |
| Timestamp rejected | Clock drift | Check server time sync |
| Duplicate events | Missing idempotency | Implement event ID tracking |
| Handler timeout | Slow processing | Use async queue |
Examples
Testing Webhooks Locally
# Use ngrok to expose local server
ngrok http 3000
# Send test webhook
curl -X POST https://your-ngrok-url/webhooks/windsurf \
-H "Content-Type: application/json" \
-d '{"type": "test", "data": {}}'
Resources
Next Steps
For performance optimization, see windsurf-performance-tuning.