Glide Apps icon

Glide Apps

Interact with Glide Apps API
Join our community

Actions17

Overview

This node integrates with Glide Apps APIs to manage tables and rows within Glide applications. Specifically, the "Delete Table" operation allows users to delete a table from a specified Glide app. This is useful for automating cleanup tasks, managing app structure dynamically, or integrating Glide data management into broader workflows.

Practical examples:

  • Automatically removing obsolete or temporary tables after processing data.
  • Cleaning up test tables created during development cycles.
  • Managing app schema changes programmatically as part of deployment pipelines.

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 using Glide Npm Api)
Tips on how to efficiently use row limits, search, confirmation, and column filters to avoid loading too much data.

Note: For the "Delete Table" operation under the "Default" resource, the key input properties relevant are:

Name Meaning
App Name or ID Select or specify the Glide app from which the table will be deleted.
Table Name or ID Select or specify the table to delete within the chosen app.

These properties are required to identify the exact table to delete.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of deletion or any error messages returned by the Glide API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Glide Apps API.
  • Supports two API types:
    • The official Big Tables API via OpenAPI specification.
    • The Glide Npm API client (@glideapps/Tables).
  • The node uses helper functions to fetch apps, tables, and rows 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 a non-existent app or table ID will result in errors indicating the resource was not found.
    • Attempting to delete a table that is in use or protected may fail depending on Glide API restrictions.

  • Error messages:

    • "Error: <message>" — Generic error wrapper returned when API calls fail; check the message for details.
    • Dropdowns may show empty lists if the API token lacks permissions or if the app/table IDs are incorrect.

  • Resolutions:

    • Verify API credentials and permissions.
    • Confirm app and table IDs exist and are accessible.
    • Use the usage tips provided when using the Npm API to avoid large data loads causing timeouts or performance issues.

Links and References

Discussion