neo4j-kafka-skill

Configure Neo4j Connector for Kafka sink and source strategies plus native CDC API cursor loops.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/eklyukin/my-ai-config --skill neo4j-kafka-skill-eklyukin
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: neo4j-kafka-skill
Source: https://github.com/eklyukin/my-ai-config/tree/main/skills/neo4j-kafka-skill
Command: npx skills add https://github.com/eklyukin/my-ai-config --skill neo4j-kafka-skill-eklyukin

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve? Setting up bidirectional streaming between Kafka and Neo4j involves choosing among multiple sink strategies (Cypher, Pattern, CDC, CUD), configuring exactly-once semantics, dead-letter queues, schema registry converters, and native CDC cursor management, all of which are error-prone without a consolidated reference. ## Core Features & Use Cases - Sink Connector Strategies: Configure Cypher, Pattern, CDC, and CUD sink strategies with idempotent MERGE patterns, exactly-once semantics via offset tracking constraints, and DLQ error handling. - Source Connector & Native CDC: Stream Neo4j changes to Kafka using CDC-based or query-based source connectors, or consume change events in-process with db.cdc.query cursor-loop patterns in Python and Java. - Use Case: A team needs to mirror Kafka user events into a Neo4j graph with exactly-once delivery and route failed messages to a dead-letter queue; the skill provides the complete production connector configuration including the required NODE KEY constraint. ## Quick Start Ask the assistant to generate a Neo4j Kafka sink connector configuration that consumes a JSON topic and upserts Person nodes with exactly-once semantics and a dead-letter queue.

Frequently Asked Questions about neo4j-kafka-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stream Kafka events into Neo4j?ā–¼

Use the Neo4j Connector for Kafka sink with a strategy matching your data: Cypher for custom transformations, Pattern for code-free field mapping, CDC for mirroring another Neo4j, or CUD for pre-formatted create/update/delete messages. Write MERGE-based queries for idempotency.

How do I stream Neo4j changes to a Kafka topic?ā–¼

Use the source connector with the CDC strategy on Neo4j 5.13+ Enterprise or Aura Business Critical, defining topic patterns and operations. For older editions, use the query-based strategy with a streaming property and $lastCheck parameter.

Does Neo4j CDC work on Community Edition?ā–¼

No, the native CDC API requires Neo4j 5.13+ Enterprise Edition, AuraDB Business Critical, or AuraDB VDC. Self-managed instances must also set db.cdc.enabled=true in neo4j.conf; Aura enables it by default on eligible tiers.

Why does my Neo4j sink connector replay messages after restart?ā–¼

Without exactly-once semantics the connector provides at-least-once delivery. Enable EOS by setting neo4j.eos-offset-label and creating a NODE KEY constraint on the offset tracking label, or ensure your Cypher uses MERGE for idempotent writes.

Why do CDC cursors become invalid after a database restore?ā–¼

Restoring Neo4j from a backup invalidates existing CDC cursors. Reconfigure the source connector's neo4j.start-from property to NOW or EARLIEST, or bootstrap a fresh cursor with db.cdc.current() or db.cdc.earliest().