couchbase-eventinglisted

# Couchbase Eventing A skill for *designing and operating* Couchbase Eventing functions — JavaScript that runs in response to document mutations in a source collection. Distinct from: - `couchbase-mcp` — calling `admin_eventing_*` tools to deploy and manage functions - `couchbase-app-integration` — SDK-based DCP consumer code for change processing outside the cluster - `couchbase-data-modeling` — document shape decisions If the conversation is "I want to run code when a document changes," this is the right skill. ## When this skill applies - "How do Eventing functions work?" - "How do I deploy an Eventing function?" - "How do I write an OnUpdate handler?" - "How do I call an external API from Eventing?" - "Can I run SQL++ from inside an Eventing function?" - "How do I sync data between two collections automatically?" - "Eventing function is deployed but nothing happens" - "How do I debug an Eventing function?" - "What's the metadata bucket / keyspace for?" - "How do I handle errors in Eventing functions?" ## Pick the right reference | Question | Read | |---|---| | "How do I write the JavaScript? OnUpdate, OnDelete, cron, curl, N1QL?" | `references/function-authoring.md` | | "How do I configure and deploy a function — source, metadata, workers, bindings?" | `references/deployment.md` | | "Function isn't triggering / processing slowly / throwing errors — what's wrong?" | `references/troubleshooting.md` | ## Three core principles **Principle 1 — Eventing is exactly-once