home / skills / jeremylongshore / claude-code-plugins-plus-skills / instantly-webhooks-events

This skill securely validates Instantly webhook signatures, handles events, and enforces idempotency to protect against replay attacks.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill instantly-webhooks-events

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
5.4 KB
---
name: instantly-webhooks-events
description: |
  Implement Instantly webhook signature validation and event handling.
  Use when setting up webhook endpoints, implementing signature verification,
  or handling Instantly event notifications securely.
  Trigger with phrases like "instantly webhook", "instantly events",
  "instantly webhook signature", "handle instantly events", "instantly notifications".
allowed-tools: Read, Write, Edit, Bash(curl:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Instantly Webhooks & Events

## Overview
Securely handle Instantly webhooks with signature validation and replay protection.

## Prerequisites
- Instantly webhook secret configured
- HTTPS endpoint accessible from internet
- Understanding of cryptographic signatures
- Redis or database for idempotency (optional)

## Webhook Endpoint Setup

### Express.js
```typescript
import express from 'express';
import crypto from 'crypto';

const app = express();

// IMPORTANT: Raw body needed for signature verification
app.post('/webhooks/instantly',
  express.raw({ type: 'application/json' }),
  async (req, res) => {
    const signature = req.headers['x-instantly-signature'] as string;
    const timestamp = req.headers['x-instantly-timestamp'] as string;

    if (!verifyInstantlySignature(req.body, signature, timestamp)) {
      return res.status(401).json({ error: 'Invalid signature' });
    }

    const event = JSON.parse(req.body.toString());
    await handleInstantlyEvent(event);

    res.status(200).json({ received: true });
  }
);
```

## Signature Verification

```typescript
function verifyInstantlySignature(
  payload: Buffer,
  signature: string,
  timestamp: string
): boolean {
  const secret = process.env.INSTANTLY_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

```typescript
type InstantlyEventType = 'resource.created' | 'resource.updated' | 'resource.deleted';

interface InstantlyEvent {
  id: string;
  type: InstantlyEventType;
  data: Record<string, any>;
  created: string;
}

const eventHandlers: Record<InstantlyEventType, (data: any) => Promise<void>> = {
  'resource.created': async (data) => { /* handle */ },
  'resource.updated': async (data) => { /* handle */ },
  'resource.deleted': async (data) => { /* handle */ }
};

async function handleInstantlyEvent(event: InstantlyEvent): 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

```typescript
import { Redis } from 'ioredis';

const redis = new Redis(process.env.REDIS_URL);

async function isEventProcessed(eventId: string): Promise<boolean> {
  const key = `instantly:event:${eventId}`;
  const exists = await redis.exists(key);
  return exists === 1;
}

async function markEventProcessed(eventId: string): Promise<void> {
  const key = `instantly:event:${eventId}`;
  await redis.set(key, '1', 'EX', 86400 * 7); // 7 days TTL
}
```

## Webhook Testing

```bash
# Use Instantly CLI to send test events
instantly webhooks trigger resource.created --url http://localhost:3000/webhooks/instantly

# 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 Instantly 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
```bash
# Use ngrok to expose local server
ngrok http 3000

# Send test webhook
curl -X POST https://your-ngrok-url/webhooks/instantly \
  -H "Content-Type: application/json" \
  -d '{"type": "test", "data": {}}'
```

## Resources
- [Instantly Webhooks Guide](https://docs.instantly.com/webhooks)
- [Webhook Security Best Practices](https://docs.instantly.com/webhooks/security)

## Next Steps
For performance optimization, see `instantly-performance-tuning`.

Overview

This skill implements Instantly webhook signature validation and secure event handling for web services. It provides a pattern for verifying HMAC signatures, rejecting replayed requests, and dispatching typed event handlers. The goal is a reliable, idempotent webhook endpoint ready for production traffic.

How this skill works

The skill verifies incoming webhook requests by computing an HMAC-SHA256 over the timestamp + payload and comparing it to the X-Instantly-Signature header using a timing-safe comparison. It rejects requests with stale timestamps to prevent replay attacks. Events are parsed and routed to registered handlers, and optional Redis-backed idempotency prevents duplicate processing.

When to use it

  • When exposing an HTTPS endpoint to receive Instantly notifications
  • When you need cryptographic verification of webhook payloads
  • When preventing replay attacks and duplicate event processing
  • When integrating Instantly events into async workflows or queues
  • When building production-grade webhook handling with retries

Best practices

  • Require the raw request body for signature calculation; do not use parsed JSON before verification
  • Reject timestamps older than 5 minutes to mitigate replay attacks
  • Use timing-safe comparison for signature checks to avoid side-channel leaks
  • Persist processed event IDs with a TTL (e.g., 7 days) to achieve idempotency
  • Log unhandled event types and surface processing failures to enable retries via non-2xx responses

Example use cases

  • Receive resource.created and resource.updated events to sync external data stores
  • Trigger asynchronous jobs (worker queue) from validated Instantly events
  • Protect admin webhook endpoints from replay and tampering
  • Use Redis to mark processed event IDs and avoid double-processing
  • Test webhooks locally with ngrok or the Instantly CLI before production rollout

FAQ

What headers are required for verification?

Use X-Instantly-Signature and X-Instantly-Timestamp. Compute HMAC over `timestamp.payload` with your webhook secret.

How do I prevent duplicate event processing?

Store each event ID (e.g., in Redis) with a TTL and check existence before handling; mark processed IDs after successful processing.

What if signature verification fails intermittently?

Confirm the configured webhook secret, ensure server clock is synced (NTP), and verify the raw body is used for HMAC calculation.