Actions6
Record → Get Many
AI-generatedOverview
This node interacts with the "Record" resource of the Teable API, specifically supporting the "Get Many" operation. It retrieves multiple records from a specified table within the Teable database platform, which offers a spreadsheet-like interface for managing data.
Common scenarios where this node is beneficial include:
- Fetching bulk data from a specific table for reporting or analysis.
- Integrating Teable data into workflows that require batch processing or synchronization.
- Querying filtered or sorted datasets to feed downstream automation steps.
Practical example:
- Retrieve all customer records from a "Customers" table, filtering by region and sorting by last purchase date.
- Get the first 100 entries from an inventory table to update stock levels in another system.
Properties
| Name | Meaning |
|---|---|
| Table ID | The unique identifier of the table to fetch records from. This ID can be found in the table URL or API documentation. |
| Return All | Whether to return all matching records or limit the number of results. Options: true (return all), false (limit results). |
| Limit | Maximum number of records to return when "Return All" is false. Minimum value is 1. Default is 50. |
| Additional Fields | A collection of optional parameters to customize the query: - Cell Format: Defines how cell values are returned. Options: JSON (structured JSON data), Text (plain text).- Field Key Type: Defines keys used in record fields. Options: Name, ID, DB Field Name.- Filter: JSON object specifying complex query conditions to filter results. - Order By: JSON array defining sorting order of records. - Projection: Comma-separated list of field names to retrieve; leave empty to get all fields. - Search: Comma-separated search terms to match records. - Skip: Number of records to skip for pagination. - View ID: Specifies a particular view ID to fetch records from. |
Output
The node outputs an array of records in the json property of each item. Each record contains fields keyed according to the selected "Field Key Type" (by name, ID, or database field name). Cell values are formatted either as structured JSON or plain text depending on the "Cell Format" setting.
No binary data output is indicated.
Dependencies
- Requires connection to the Teable API via an API key credential.
- The base URL for the API is configured through credentials.
- The node sends HTTP requests to the Teable API endpoints to fetch records.
Troubleshooting
- Invalid Table ID: If the provided Table ID is incorrect or does not exist, the API will likely return an error. Verify the Table ID from the Teable UI or API docs.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
- Malformed Filter or Order By JSON: Incorrectly formatted JSON in the "Filter" or "Order By" fields may cause request errors. Validate JSON syntax before use.
- Limit and Pagination Issues: Setting "Return All" to false but omitting or misconfiguring the "Limit" or "Skip" properties may result in unexpected numbers of records returned.
- Unsupported Field Keys or Projections: Using field keys or projections that do not exist in the table schema may lead to empty or partial results.
Links and References
- Teable API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- JSON formatting tools for validating filter and orderBy inputs (e.g., https://jsonlint.com/)