Actions13
Overview
This node interacts with a Table resource in the Tulip API, specifically to look up a single record by its ID. It allows users to select a table and then specify a record within that table to retrieve detailed information. Additionally, users can specify which fields (columns) of the record they want to fetch.
Common scenarios include:
- Retrieving detailed data about a specific item or entry stored in a Tulip table.
- Fetching selective columns from a record for further processing or conditional logic in an automation workflow.
- Integrating Tulip table data into other systems by extracting precise records on demand.
For example, you might use this node to get the status and assigned operator of a particular machine maintenance record identified by its unique record ID.
Properties
| Name | Meaning |
|---|---|
| Table Name or ID | Select the target table from a dropdown list or specify its ID via expression. |
| Record Name or ID | Select the specific record within the chosen table by name or ID, or specify it via expression. |
| Fields | A collection of columns to retrieve from the record. Each column is selected from the available columns in the table. |
The "Fields" property supports multiple values, allowing you to specify exactly which columns you want returned for the record lookup.
Output
The node outputs JSON data representing the looked-up record. The structure includes key-value pairs where keys correspond to the selected column names or IDs, and values are the respective data from the record.
If binary data were supported, it would be summarized here, but based on the provided code and properties, the output is purely JSON with the requested fields.
Dependencies
- Requires connection to the Tulip API using an API authentication credential.
- Needs proper configuration of the Tulip API credentials in n8n.
- Relies on dynamic loading methods to populate options for tables, records, and columns (
getTables,getRecordsIDs,getColumns), which depend on the Tulip API responses.
Troubleshooting
- Empty or missing record: If the specified record ID does not exist in the selected table, the node may return empty data or an error. Verify the record ID and table selection.
- Invalid field names: Specifying columns that do not exist in the table will likely cause errors or empty results. Use the dropdown to select valid columns or ensure expressions resolve correctly.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to access the tables and records.
- Load options failing: If the dropdowns for tables, records, or columns fail to load, check network connectivity and API access rights.
Links and References
- Tulip API Documentation (general reference for API endpoints)
- n8n Expressions Documentation (for using expressions in property fields)