Actions13
Table → Lookup a Table
AI-generatedOverview
This node integrates with the Tulip API to perform operations related to tables and machines within the Tulip platform. Specifically, for the "Table" resource and the "Lookup a Table" operation, it allows users to retrieve detailed information about a specific table by selecting its name or ID. This is useful in scenarios where you want to fetch metadata or data associated with a particular table in Tulip for further processing or automation workflows.
Practical examples include:
- Fetching a table's schema or contents to use in downstream workflow steps.
- Validating the existence of a table before performing updates or inserts.
- Integrating Tulip table data into other systems via n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Table Name or ID | Select a table from a dropdown list populated dynamically or specify a table ID using an expression. |
The dropdown options are loaded dynamically from the Tulip API, allowing users to pick from existing tables without manually entering IDs.
Output
The node outputs JSON data representing the details of the looked-up table. This typically includes the table's metadata and possibly its content depending on the API response structure. The output is accessible via the json property of the node's output items.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Tulip API via an API key credential configured in n8n.
- The node depends on the Tulip API being available and responsive.
- Dynamic loading of table options requires proper permissions to list tables in the connected Tulip account.
Troubleshooting
Common issues:
- Failure to load table options: Ensure the API key has permission to list tables.
- Lookup failure due to invalid or missing table ID: Verify that the table ID or name is correct and exists.
- Network or authentication errors: Check API credentials and network connectivity.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; reconfigure credentials.
- "Table not found" errors suggest the specified table ID does not exist; verify input.
- Timeout or connection errors may require retrying or checking network settings.
Links and References
- Tulip API Documentation (general reference for API endpoints)
- n8n Expressions Documentation (for using expressions in property fields)