Actions17
- Tables Actions
- Rows Actions
- Stashes Actions
Overview
This node allows users to create new tables within Glide Apps using two different API methods: the Big Tables API (OpenAPI) or the Glide NPM API. It is designed for automating the creation of structured data tables that can be linked to one or more apps in Glide. This is particularly useful for workflows that require dynamic table generation based on incoming data, such as generating invoices, managing customer records, or tracking orders.
Practical examples include:
- Automatically creating an "Invoices" table with predefined columns and rows when a new billing cycle starts.
- Generating a custom data table linked to multiple Glide apps for synchronized data sharing.
- Creating tables with schema inferred from provided data or explicitly defined schemas for consistent data structure.
Properties
| Name | Meaning |
|---|---|
| API Type | Choose which Glide API to use for this operation: - Big Tables API (OpenAPI) - Glide Npm Api (@glideapps/Tables) |
| Name | The name of the table to create. Required if not included in the request body. Must not be duplicated in both query and body. Example: Invoices |
| Apps To Link | An array of app IDs to link the newly created table to. This links the table across multiple Glide apps for shared access. |
| On Schema Error | Defines how to handle data that does not match the table schema: - abort: Stop operation and return error - dropColumns: Ignore problematic columns in affected rows - updateSchema: Adjust schema automatically to fit data |
| Schema | JSON object defining the table schema as a collection of column definitions. If omitted, the schema will be inferred from the data rows. Columns have properties like id, displayName, and type. |
| Rows | JSON array of row objects matching the table schema. Each object’s keys correspond to column IDs and values to cell data. Example: list of invoices with fields like fullName, invoiceDate, totalAmount, amountPaid. |
Output
The node outputs JSON data representing the newly created table resource as returned by the Glide API. This typically includes metadata about the table such as its ID, name, linked apps, schema details, and the rows inserted. The output enables downstream nodes to reference or manipulate the created table further.
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 methods:
- Big Tables API via OpenAPI specification.
- Glide NPM API client library.
- The node expects proper configuration of credentials and network access to Glide's API endpoints.
Troubleshooting
Error: Passing table name in both query and body
Ensure the table name is provided either as a query parameter or in the request body, but not both simultaneously.Schema mismatch errors
If the data rows do not conform to the schema, the node may abort or drop columns depending on theOn Schema Errorsetting. Adjust this property to control behavior or fix the schema/data accordingly.Invalid JSON in Schema or Rows
TheSchemaandRowsinputs expect valid JSON. Malformed JSON will cause parsing errors. Validate JSON syntax before running.API authentication failures
Verify that the API key credential is correctly set up and has sufficient permissions to create tables.Linking to invalid app IDs
When specifyingApps To Link, ensure the app IDs exist and are accessible; otherwise, linking may fail silently or cause errors.
Links and References
- Glide Apps API Documentation
- Glide Tables NPM Package
- n8n Expressions Documentation (for dynamic property values)
