Tulip icon

Tulip

Consume Tulip API

Actions13

Table → Delete a Record

AI-generated

Overview

This node interacts with a Table resource in the Tulip API, specifically to delete a record from a specified table. It is useful when you want to programmatically remove entries from your data tables within Tulip, for example, deleting outdated or incorrect records automatically as part of a workflow.

Practical examples include:

  • Automatically removing user-submitted form entries after processing.
  • Cleaning up temporary or test data from a table.
  • Deleting inventory items that are no longer available.

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 the record will be deleted from.
Record Name or ID Select the specific record to delete from the chosen table, either from a list or by specifying its ID using an expression.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this includes confirmation of deletion or details about the deleted record. The exact structure depends on the API response but generally confirms success or failure.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Tulip API.
  • Needs network access to the Tulip service endpoint.
  • The node uses internal methods to load options dynamically for tables and records, so proper API permissions to list tables and records are necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent table or record ID will cause errors.
    • Insufficient permissions or expired API credentials can lead to authentication failures.
    • Network connectivity problems may prevent the node from reaching the Tulip API.

  • Error messages:

    • Errors indicating "record not found" suggest the specified record ID does not exist in the selected table.
    • Authentication errors imply issues with the provided API key or credential setup.
    • Timeout or connection errors indicate network issues or API unavailability.

  • Resolutions:

    • Verify the table and record IDs are correct and accessible.
    • Ensure the API key credential is valid and has required permissions.
    • Check network connectivity and retry if transient errors occur.

Links and References

Discussion