Actions17
- Tables Actions
- Rows Actions
- Stashes Actions
Overview
This node allows users to interact with Glide Apps tables via two different APIs: the Big Tables API (OpenAPI) or the Glide NPM API. Specifically, for the "Tables" resource and the "Get Tables" operation, it fetches a list of tables from a specified Glide app.
Common scenarios where this node is beneficial include:
- Automating workflows that require retrieving table metadata or data from Glide apps.
- Integrating Glide app tables with other systems by fetching table lists dynamically.
- Building dashboards or reports based on Glide app data.
Practical example:
- A user wants to retrieve all tables from a specific Glide app to display their names in another system or to process them further in an automation workflow.
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 API Type is "Glide Npm Api") Helpful tips for using the node effectively: - Use Row Limit and Row Search to avoid loading too much data. - Enable Confirm Row Fetch for large tables to prevent accidental data loads. - Use Column Type Filter to show only certain column types. - All dropdowns support expressions for advanced use. |
Output
The node outputs JSON data representing the list of tables retrieved from the Glide app. Each item in the output array typically contains table metadata such as table name and ID.
If binary data were supported, it would be summarized here, but this node focuses on JSON output only.
Dependencies
- Requires an API key credential for authenticating with the Glide Apps API.
- Supports two API methods:
- The Big Tables API via OpenAPI specification.
- The Glide NPM API (
@glideapps/Tablespackage).
- The node uses helper functions to load options dynamically (e.g., apps, tables, rows) based on the selected API type.
- Requires network access to
https://api.glideapps.com.
Troubleshooting
Common issues:
- Authentication errors due to missing or invalid API credentials.
- Empty results if the specified app ID does not contain any tables or if permissions are insufficient.
- Large data loads causing timeouts or performance issues; mitigated by using row limits and search filters when applicable.
Error messages:
- Errors returned from the Glide API will be shown with their message prefixed by "Error:" in dropdowns or execution results.
- If no tables are found or an error occurs during fetching, the node returns an empty array or an error object with a descriptive message.
Resolutions:
- Verify that the API key credential is correctly configured and has necessary permissions.
- Double-check the app ID and ensure it exists and is accessible.
- Use filtering options and confirmation toggles to manage large datasets safely.
