Cache Node

The Cache node deduplicates events and enriches payloads with cached data. Drop duplicate events based on a payload key, or attach previously-seen data to new events passing through the node.

Overview

Webhook sources sometimes send duplicate events — Stripe, for example, may retry a webhook delivery even if the first attempt succeeded. The Cache node addresses this with two capabilities:

• Deduplication — Tracks event signatures based on a payload field (keyField). If an event with the same key value arrives within the TTL window, it is silently dropped.
• Enrichment — Attaches previously-cached payload data to new events. The cached data is merged into the enrichTargetField (defaults to _cached).

Configuration

Create a Cache Node

curl -X POST /api/cache-nodes \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Stripe Event Dedup",
    "keyField": "id",
    "ttlSeconds": 3600,
    "deduplicateEnabled": true,
    "isActive": true
  }'

Response

{
  "_id": "6656a3b4c5d6e7f8a9b0c1d2",
  "name": "Stripe Event Dedup",
  "keyField": "id",
  "ttlSeconds": 3600,
  "deduplicateEnabled": true,
  "enrichEnabled": false,
  "enrichTargetField": "_cached",
  "inputNodes": [],
  "inputNodes": [],
  "inputNodes": [],
  "outputWebhookIds": [],
  "outputTransformIds": [],
  "outputNodes": [],
  "filters": [],
  "isActive": true,
  "createdAt": "2025-05-01T12:00:00.000Z",
  "updatedAt": "2025-05-01T12:00:00.000Z"
}

Update a Cache Node

curl -X PATCH /api/cache-nodes/6656a3b4c5d6e7f8a9b0c1d2 \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "ttlSeconds": 7200,
    "enrichEnabled": true
  }'

Canvas Integration

The Cache node is available as a canvas node. Connect webhooks or scheduled webhooks as inputs, and webhooks or transforms as outputs. Events flow through the cache, which applies deduplication and/or enrichment before forwarding to output nodes.

Payload Examples

First occurrence — passes through

{
  "id": "evt_stripe_abc123",
  "type": "payment_intent.succeeded",
  "data": {
    "object": { "amount": 5000, "currency": "usd" }
  }
}
// Cache key: "evt_stripe_abc123" — NOT in cache
// Result: PASSES through, key stored with TTL

Duplicate — deduplicated

{
  "id": "evt_stripe_abc123",
  "type": "payment_intent.succeeded",
  "data": {
    "object": { "amount": 5000, "currency": "usd" }
  }
}
// Cache key: "evt_stripe_abc123" — FOUND in cache (within TTL)
// deduplicateEnabled: true
// Result: DROPPED — duplicate event discarded

Enrichment — cached data attached

{
  "id": "evt_stripe_def456",
  "type": "payment_intent.succeeded",
  "data": { "amount": 3000 },
  "_cached": {
    "id": "evt_stripe_def456",
    "type": "payment_intent.created",
    "data": { "amount": 3000, "status": "requires_payment_method" }
  }
}
// enrichEnabled: true, enrichTargetField: "_cached"
// Previous event with same key is attached under _cached

Use Cases

• Webhook deduplication — Stripe sends the same webhook 2-3 times as retries. The cache detects the duplicate key and silently drops repeated deliveries so each event is processed only once.
• Idempotency enforcement — Guarantee that duplicate webhook calls do not cause duplicate side effects in your system.
• Payload enrichment — The first event carries user info, the second event carries order info. The cache enriches the second event with the user data from the first, so downstream nodes receive a complete picture without additional API calls.
• Burst protection — During high-volume periods, deduplicate rapid-fire events that carry the same payload.
• Testing and replay — When replaying events for testing, the cache prevents downstream services from being hit with previously-processed events.

API Reference