Xano icon

Xano

Interact with Xano API to manage workspaces, tables, and content.

Overview

This node integrates with the Xano API to manage data within workspaces and tables. Specifically, the "Delete a Row" operation under the "Table" resource allows users to delete a single row from a specified table in a workspace by providing the row's unique identifier.

Common scenarios for this node include:

  • Removing outdated or incorrect records from a database table.
  • Automating cleanup tasks where certain rows need to be deleted based on external triggers.
  • Managing data lifecycle by programmatically deleting entries after processing.

For example, you might use this node to delete a user record from a customer database when they unsubscribe from a service.

Properties

Name Meaning
Workspace Name or ID Select or specify the workspace containing the target table.
Table Name or ID Select or specify the table from which the row will be deleted.
Row ID (Field to search by) Fixed as "ID" — the field used to identify the row to delete.
Field Value The actual ID value of the row to delete (e.g., "123").

Output

The node outputs JSON data representing the result of the delete operation. Typically, this includes confirmation that the row was successfully deleted or an error message if the deletion failed.

If the node supports binary data output, it would generally relate to any file or media content associated with the deleted row, but this is not indicated here.

Dependencies

  • Requires an API key credential for authenticating with the Xano API.
  • The node depends on the Xano API being accessible and the provided workspace, table, and row IDs being valid.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Invalid Workspace or Table ID: If the workspace or table does not exist or the ID is incorrect, the node will fail to find the target and throw an error. Verify IDs and permissions.
  • Row Not Found: If the specified row ID does not exist in the table, the node may return an error indicating no matching record found.
  • Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Network Issues: Connectivity problems with the Xano API endpoint can cause timeouts or failures.

To resolve errors:

  • Double-check all input IDs and values.
  • Confirm API credentials are valid and active.
  • Review API limits or restrictions on the Xano side.

Links and References

Discussion