Use CDC to query changes (procedures)

This feature has been released as a public beta in AuraDB Enterprise October Release and Neo4j Enterprise Edition 5.13 and breaking changes are likely to be introduced before it is made generally available (GA).

Once CDC is enabled, there are a number of Cypher procedures that you may use to query changes.

CDC works with change identifiers, which are essentially pointers to specific transactions. The CDC procedures allow you to retrieve specific change identifiers or to query for changes that affected the database after a given change identifier.

The easiest way to see CDC in action is by retrieving the earliest change identifier, creating a new node in the database, and then querying for changes using the earliest change identifier.

Change identifiers are local to the database they are generated for, and cannot be used to query changes on another database. Keep this in mind when restoring a database from a backup, since the restored database is practically a new database. See restore from backup for details.

Retrieve the earliest change identifier

The procedure db.cdc.earliest returns the change identifier for the earliest available change.

Example 1. Query earliest change identifier
CALL db.cdc.earliest()
Table 1. Result


Retrieve the current change identifier

The procedure db.cdc.current returns the change identifier for the last committed transaction.

Note that the returned identifier is exclusive, meaning it does not include the changes that happened in the transaction it points to.

Example 2. Query current change identifier
CALL db.cdc.current()
Table 2. Result


Query changes

The procedure db.cdc.query returns the changes that happened to the database after the given change identifier.

    from =  :: STRING?, (1)
    selectors = [] :: LIST? OF MAP? (2)
) :: (
    id :: STRING?, (3)
    txId :: INTEGER?, (4)
    seq :: INTEGER?, (5)
    metadata :: MAP?, (6)
    event :: MAP? (7)
1 The change identifier to query changes from, either captured from an earlier call to db.cdc.query or from one of db.cdc.current or db.cdc.earliest. The default value is "" (empty string) which is replaced with db.cdc.current implicitly. This value is treated as exclusive, so the results of the query do not include the changes that happened on the transaction corresponding to this change identifier.
2 An optional list of selectors to filter out changes. The default is an empty list, which means all changes are returned, without any filtering.
3 The unique change identifier associated with each change record. Each of these can be used for further db.cdc.query calls.
4 A number identifying which transaction the change happened in, unique in combination with seq. Transaction identifiers are not continuous (some transactions, such as system and schema commands, are not recorded in change data capture and cause gaps in the transaction identifiers).
5 A number used for ordering changes that happened in the same transaction. Note that the order of changes observed in the output does not necessarily correspond to the order in which changes were applied during the transaction.
6 A map of values containing transaction metadata. This is the same for all of the changes in a single transaction. For a detailed description of the metadata fields, see Format of change events.
7 The retrieved changes on the affected entity. For a detailed description of the change event, see Format of change events.
Example 3. Query for changes after creation of a :Person node
Table 3. Result
id txId seq metadata event




  "txStartTime": "2024-04-03T06:28:19.630000000Z",
  "databaseName": "neo4j",
  "executingUser": "neo4j",
  "authenticatedUser": "neo4j",
  "connectionServer": "",
  "connectionType": "bolt",
  "serverId": "20668765",
  "captureMode": "FULL",
  "connectionClient": "",
  "txCommitTime": "2024-04-03T06:28:19.651000000Z",
  "txMetadata": {
    "app": "neo4j-browser_v5.15.0",
    "type": "user-direct"
  "elementId": "4:68262997-88e3-4518-83ec-d944674609f4:8",
  "operation": "c",
  "keys": {

  "labels": [
  "state": {
    "after": {
      "labels": [
      "properties": {
        "name": "Stefano"
    "before": null
  "eventType": "n"