Tulip icon

Tulip

Consume Tulip API

Actions13

Table → Look up a Record

AI-generated

Overview

This node integrates with the Tulip API to look up a specific record in a chosen table. It allows users to select a table and then specify a record within that table by its name or ID. Additionally, users can filter which fields (columns) of the record they want to retrieve. This operation is useful when you need to fetch detailed information about a particular entry from a structured dataset managed in Tulip.

Common scenarios:

  • Retrieving detailed data for a specific product or item stored in a Tulip table.
  • Fetching user or employee records by their unique identifiers.
  • Accessing configuration or status records dynamically during workflow execution.

Practical example:
You have a table named "Inventory" and want to get details about a specific product by its record ID. You use this node to select the "Inventory" table, specify the product's record ID, and choose which columns (e.g., "Price", "Stock Level") to return for further processing or decision-making in your workflow.

Properties

Name Meaning
Table Name or ID Select the target table from a list or specify its ID via an expression.
Record Name or ID Select the specific record within the chosen table by name or ID, or specify it using an expression.
Fields A collection of columns to filter the query by; choose one or more columns from the selected table whose values you want to retrieve.

Output

The node outputs JSON data representing the looked-up record from the specified table. The output includes only the fields (columns) requested in the input properties. The structure corresponds to the key-value pairs of the selected columns and their respective values for the identified record.

If the node supports binary data output (not indicated here), it would typically represent file attachments or media associated with the record, but this operation focuses on JSON data retrieval.

Dependencies

  • Requires access to the Tulip API.
  • Needs an API authentication token configured as credentials in n8n.
  • The node depends on dynamic loading methods to populate options for tables, records, and columns, which require proper API connectivity.

Troubleshooting

  • Common issues:

    • Failure to load tables, records, or columns options usually indicates connectivity problems or insufficient permissions.
    • Specifying incorrect or non-existent record IDs will result in no data found or errors.
    • Omitting required fields like table or record ID will cause validation errors.

  • Error messages and resolutions:

    • "Record not found": Verify the record ID exists in the selected table.
    • "Unauthorized" or "Authentication failed": Check that the API key credential is valid and has necessary permissions.
    • "Failed to load options": Ensure the API endpoint is reachable and the network connection is stable.

Links and References

Discussion