Tulip icon

Tulip

Consume Tulip API

Actions13

Overview

This node interacts with the Tulip API to delete all records from a specified table. It is useful in scenarios where you need to clear out data from a table entirely, such as resetting datasets, cleaning up test data, or preparing tables for fresh input. For example, if you have a table tracking inventory and want to remove all entries before importing new stock data, this operation would be appropriate.

Properties

Name Meaning
Table Name or ID Select the target table from a list or specify its ID via an expression. This determines which table's records will be deleted.
Allow Records In Use Boolean option that, if set to true, skips checking whether records are currently used by running Tulip apps. If records are in use, those apps may malfunction.

Output

The node outputs JSON data indicating the result of the deletion operation. Typically, this includes confirmation that all records were deleted successfully or details about any issues encountered. The output does not include binary data.

Dependencies

  • Requires an active connection to the Tulip API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node depends on the Tulip API’s ability to list tables and perform record deletions.

Troubleshooting

  • Common Issues:

    • Attempting to delete records from a table currently in use by running apps without enabling "Allow Records In Use" may cause errors or app malfunctions.
    • Providing an invalid table name or ID will result in failure to locate the table.
    • Insufficient permissions or expired API tokens can cause authorization errors.

  • Error Messages:

    • "Table not found": Verify the table name or ID is correct and accessible.
    • "Records in use": Enable the "Allow Records In Use" option if you understand the risks.
    • "Unauthorized" or "Authentication failed": Check API credentials and refresh tokens if necessary.

Links and References

Discussion