Actions13
Overview
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 it from a list or specifying its 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 configuration or schema details of a table before performing data transformations.
- Retrieving table data to use as input for other nodes or systems.
- Automating reporting or monitoring tasks based on table contents.
Properties
| Name | Meaning |
|---|---|
| Table Name or ID | Select a table from a dropdown list populated dynamically or specify a table ID using an expression. |
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. The output is structured as standard JSON objects accessible via the json property of each item.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Tulip API.
- The node depends on the Tulip API being accessible and the provided credentials having sufficient permissions to read table data.
- No additional environment variables or external services are explicitly required beyond the API authentication.
Troubleshooting
Common Issues:
- Invalid or expired API credentials will cause authentication failures.
- Specifying a non-existent table ID or name will result in errors or empty responses.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- "Table not found" or similar messages suggest the specified table does not exist or is inaccessible; check the table ID or name.
- Timeout or connection errors may require checking network settings or API availability.
Links and References
- Tulip API Documentation (general reference for API endpoints and usage)
- n8n Expressions Documentation (for using expressions to specify dynamic values)