Glide Apps icon

Glide Apps

Interact with Glide Apps API
Join our community

Actions17

Overview

This node operation updates a specific row in a Glide table by its unique row ID. It supports two API types: the Big Tables API (OpenAPI) and the Glide NPM API, allowing flexibility depending on user preference or environment.

Typical use cases include:

  • Modifying existing data entries in Glide tables programmatically.
  • Synchronizing external data sources with Glide tables by updating rows based on changes.
  • Automating workflows that require conditional updates to table rows, such as status changes or data corrections.

For example, you might use this node to update a user's profile information stored in a Glide table when they submit a form elsewhere, or to mark an order as shipped by updating the corresponding row's status field.

Properties

Name Meaning
API Type Choose which Glide API to use for this operation:
- Big Tables API (OpenAPI)
- Glide Npm Api (@glideapps/Tables)
If Match ETag of the current table version. If provided, the update will fail if the row has been modified since this version. This helps prevent overwriting concurrent changes.
Table ID The unique identifier of the table containing the row to update, e.g., 2a1bad8b-cf7c-44437-b8c1-e3782df6.
Row ID The unique identifier of the row to update, e.g., zcJWnyI8Tbam21V34K8MNA.
On Schema Error Defines how to handle data that does not match the table schema:
- abort: Stop the operation and return an error.
- dropColumns: Ignore problematic columns and proceed.
- updateSchema: Adjust schema automatically.

Output

The node outputs JSON data representing the updated row after the operation completes successfully. This typically includes the row's fields with their new values reflecting the update.

If binary data is involved (not indicated explicitly here), it would represent any file attachments or media associated with the row, but this operation primarily deals with JSON data updates.

Dependencies

  • Requires an API key credential for authenticating with the Glide Apps API.
  • Supports two API methods:
    • Big Tables API via OpenAPI specification.
    • Glide NPM API (@glideapps/Tables package).
  • Proper configuration of the API credentials and network access to Glide's endpoints is necessary.

Troubleshooting

  • ETag Mismatch Errors: If using the "If Match" property, updates may fail if the row was changed since the ETag was retrieved. To resolve, fetch the latest ETag before updating or omit this header if concurrency control is not needed.
  • Schema Errors: When the input data contains columns not matching the table schema, errors can occur depending on the "On Schema Error" setting. Choosing updateSchema allows automatic schema adjustments, while abort requires manual correction.
  • Invalid Table or Row IDs: Ensure that the provided Table ID and Row ID are correct and exist in the Glide app; otherwise, the update will fail.
  • API Type Selection: Using the wrong API type for your environment or credentials may cause failures. Confirm which API your credentials support.
  • Network Issues: Connectivity problems or incorrect base URL configurations can lead to request failures.

Links and References

Discussion