Glide Apps icon

Glide Apps

Interact with Glide Apps API
Join our community

Actions17

Overview

This node operation "Add Rows To Table" under the "Rows" resource allows users to add new rows of data into a specified table within a Glide app. It supports two API types for interaction: the Big Tables API (OpenAPI) and the Glide NPM API. The node is useful in scenarios where automated workflows need to insert or append data records into Glide tables, such as logging form submissions, syncing external data sources, or batch importing data.

Practical examples include:

  • Adding new customer orders from an e-commerce platform into a Glide app's order tracking table.
  • Importing survey responses collected externally into a Glide app for analysis.
  • Automatically appending new inventory items into a product catalog table.

Properties

Name Meaning
API Type Choose which Glide API to use for this operation. Options: "Big Tables API (OpenAPI)" or "Glide Npm Api (@glideapps/Tables)".
Table ID The unique identifier of the target table where rows will be added. Example format: 2a1bad8b-cf7c-44437-b8c1-e3782df6. Required when using the OpenAPI type.
On Schema Error Defines how to handle cases where the input row data does not match the table schema. Options:
- abort: Stop the operation and return an error.
- dropColumns: Ignore columns causing errors and import others.
- updateSchema: Modify the schema to accommodate new or wider columns, then import.
Body JSON object representing the row data to add. Keys correspond to column IDs, values are the respective cell values. Must conform to the table schema or be handled according to the "On Schema Error" setting. Example:
json<br>{<br> "fullName": "Alex Bard",<br> "invoiceDate": "2024-07-29T14:04:15.561Z",<br> "totalAmount": 34.5,<br> "amountPaid": 0<br>}<br>

Output

The node outputs JSON data representing the result of the add row operation. This typically includes confirmation details such as the newly created row's ID and any metadata returned by the Glide API. If binary data were involved (not indicated here), it would represent file attachments or media related to the row.

Dependencies

  • Requires an API key credential for authenticating with the Glide Apps API.
  • Depending on the selected API type, either the Big Tables OpenAPI endpoint or the Glide NPM API package is used.
  • Network access to https://api.glideapps.com is necessary.
  • Proper configuration of the node’s credentials and permissions to write to the target table.

Troubleshooting

  • Schema Mismatch Errors: If the input row data contains columns not present in the table schema or incompatible data types, errors may occur unless "On Schema Error" is set to update the schema or drop problematic columns.
  • Invalid Table ID: Providing an incorrect or non-existent table ID will cause the operation to fail.
  • Authentication Failures: Missing or invalid API credentials will prevent successful API calls.
  • JSON Parsing Issues: The "Body" property must be valid JSON; malformed JSON will cause errors.
  • API Type Misconfiguration: Selecting an API type without proper setup or dependencies may lead to failures.

To resolve these issues:

  • Verify the table ID and ensure it exists.
  • Check and refresh API credentials.
  • Validate the JSON structure of the row data.
  • Adjust the "On Schema Error" setting based on your tolerance for schema changes.
  • Confirm network connectivity to the Glide API endpoints.

Links and References

Discussion