Actions4
- Table Actions
Overview
This node integrates with the Glide Tables API to manage data within Glide Apps. Specifically, the Delete Row operation under the Table resource allows users to delete one or multiple rows from a specified table in a Glide App.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or invalid data entries in Glide tables.
- Synchronizing external data sources by removing rows that no longer exist or are relevant.
- Managing user-generated content by programmatically deleting rows based on certain triggers or conditions.
For example, you could use this node to delete rows representing completed tasks from a task management Glide app or remove user records flagged as inactive.
Properties
| Name | Meaning |
|---|---|
| App ID | The identifier of the Glide App where the table resides. Can be selected from a list or entered manually. |
| Table Name | The name or ID of the Glide Table from which to delete rows. Depends on the selected App ID. Can be selected from a list or entered manually. |
| Row ID | The unique identifier of the row to delete. Required for each execution item. |
Output
The output is a JSON array containing the response from the Glide API after attempting to delete the specified rows. Each element corresponds to the result of a mutation request for a row deletion.
The structure typically includes confirmation of the deletion or any error details returned by the API.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Glide API.
- The node uses HTTP POST requests to the Glide API endpoints to perform mutations.
- Proper configuration of the API authentication credential in n8n is necessary.
- The "App ID" and "Table Name" must correspond to existing resources accessible via the authenticated account.
Troubleshooting
Common Issues:
- Invalid or missing App ID or Table Name will cause the API call to fail.
- Providing an incorrect or non-existent Row ID will result in an error or no action.
- Insufficient permissions or expired API credentials can lead to authentication errors.
Error Messages:
- Operation not supported: This occurs if an unsupported operation is requested; ensure "Delete Row" is selected.
- Resource not supported: This indicates the resource parameter is incorrect; verify "Table" is selected.
- API errors related to authorization or resource existence will be passed through from the Glide API; check your credentials and resource identifiers.
Resolution Tips:
- Double-check that the App ID and Table Name are correct and accessible.
- Verify that the Row ID exists in the specified table.
- Ensure the API key credential is valid and has appropriate permissions.
- Use the "From List" mode to select App ID and Table Name to reduce manual entry errors.