Actions17
- Tables Actions
- Rows Actions
- Stashes Actions
Overview
This node allows users to interact with Glide Apps tables and rows, specifically supporting the deletion of a row identified by its table ID and row ID. It supports two API types: the Big Tables API (OpenAPI) and the Glide NPM API. The node is useful for automating data management tasks within Glide Apps, such as removing outdated or incorrect entries from tables.
Practical examples include:
- Automatically deleting user-submitted form entries after processing.
- Cleaning up temporary or test data rows in a Glide App table.
- Removing specific records based on workflow conditions.
Properties
| Name | Meaning |
|---|---|
| API Type | Choose which Glide API to use for this operation: - Big Tables API (OpenAPI) - Glide Npm Api (@glideapps/Tables) |
| Usage Tips | (Shown only if "Glide Npm Api" is selected) Helpful tips for using the npm API effectively, including limiting rows fetched and filtering columns. |
Additional properties relevant to this DELETE operation (inferred from bundled code and context):
| Name | Meaning |
|---|---|
| App Name or ID | Select or specify the Glide App to operate on. |
| Table Name or ID | Select or specify the table containing the row to delete. |
| Row Name or ID | Select or specify the row to delete within the chosen table. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the row was successfully deleted or provide error information if the operation failed.
No binary data output is indicated.
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/Tablespackage).
- The node uses helper functions to fetch apps, tables, rows, and columns dynamically for dropdown selections.
- Requires network access to
https://api.glideapps.com.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying non-existent app, table, or row IDs will result in errors.
- Large tables without proper row limits or confirmation may cause performance issues or accidental data loads.
Error Messages:
- Errors returned from the Glide API will be surfaced, typically indicating the reason (e.g., "Row not found", "Unauthorized").
- If dropdown loading fails, the node returns an error message prefixed with "Error:" followed by the error detail.
Resolutions:
- Ensure valid API credentials are configured.
- Verify that the app, table, and row IDs exist and are accessible.
- Use the provided usage tips when working with large datasets to avoid timeouts or excessive data fetching.