Firebase Realtime Database icon

Firebase Realtime Database

Utilities for Firebase Realtime Database (scaffold)

Actions5

Update

AI-generated

Overview

This node performs an update operation on a specified path in a Firebase Realtime Database. It allows updating one or more keys at the given JSON path using Firebase's PATCH semantics. The node supports atomic writes using ETag for concurrency control, with options to fetch the ETag automatically or provide it from input. It can use either custom fields or the entire input item's JSON as the update payload. The node also supports retrying the update operation in case of ETag conflicts and offers different return modes including default, silent, or key-only responses.

Use Case Examples

  1. Updating user profile data at a specific path in Firebase Realtime Database.
  2. Performing atomic updates to prevent overwriting changes made by other clients.
  3. Using input JSON directly to update multiple fields in a database record.

Properties

Name Meaning
Database URL Base URL of your Firebase Realtime Database (without trailing slash). Required to specify the target database.
Path JSON path within the database to update. Leading slash is allowed but removed internally.
Atomic Write (ETag) Enables atomic update using ETag to ensure concurrency control. When true, the update will only succeed if the ETag matches.
ETag Source Determines how the ETag is obtained when atomic write is enabled. Can be auto-fetched or provided from input.
ETag The ETag value to use for atomic update if ETag Source is set to 'From Input'.
Max Retries Number of retry attempts for the update operation if an ETag conflict (HTTP 412) occurs.
Use Input Item JSON If true, uses the entire input item's JSON as the update payload instead of custom fields.
Return Controls the response returned by the node after the update operation.

Output

JSON

  • json - The JSON response from the Firebase Realtime Database update operation, containing the updated data or status.

Dependencies

  • Requires a Google Firebase Realtime Database OAuth2 API credential for authentication.

Troubleshooting

  • If the update operation fails with HTTP 412 Precondition Failed, it indicates an ETag mismatch. Increase 'Max Retries' or ensure the correct ETag is used.
  • Ensure the 'Database URL' and 'Path' are correctly specified without trailing or leading slashes respectively.
  • If using 'Use Input Item JSON', verify the input JSON structure matches the expected update format.
  • Check that the OAuth2 credentials are valid and have appropriate permissions to access the Firebase Realtime Database.

Discussion