Actions8
Overview
The "Search Row" operation in the Table resource allows users to query rows within a specified table in a workspace by applying search criteria. It supports pagination, sorting, and flexible search conditions defined as JSON objects matching the table schema. This node is useful for retrieving filtered data from large datasets stored in tables, enabling workflows that require dynamic data lookup or conditional processing based on table content.
Practical examples:
- Searching for customer records in a CRM table where the customer's status matches certain criteria.
- Retrieving product entries sorted by price or date added.
- Filtering orders placed within a specific date range or by order status.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | Select or specify the workspace containing the target table. |
| Table Name or ID | Select or specify the table within the workspace to search rows in. |
| Page | The page number of results to fetch (for pagination). |
| Items per Page | Number of rows to return per page. |
| Sort By Name or ID | Field name or ID to sort the search results by. |
| Sort Order | Direction of sorting: Ascending or Descending. |
| Items (JSON Array) | JSON array where each object defines search criteria for rows. Field names must match the table schema. |
Output
The node outputs JSON data representing the rows found according to the search criteria. Each item corresponds to a row in the table with fields matching the table's schema. If binary data is present in the table, it would be included accordingly, but this operation primarily returns structured JSON data.
Dependencies
- Requires an API key credential to authenticate with the external service managing workspaces and tables.
- Depends on the external API to provide workspace, table, and field metadata for loading options dynamically.
- Pagination and sorting depend on the API's support for these features.
Troubleshooting
Common issues:
- Incorrect workspace or table IDs may cause errors or empty results.
- Malformed JSON in the "Items (JSON Array)" property can lead to parsing errors.
- Sorting by a non-existent field will likely result in an error or ignored sort.
- Pagination parameters out of range may return empty pages.
Error messages and resolutions:
- "Invalid workspace or table ID": Verify the selected workspace and table exist and are accessible.
- "Failed to parse JSON input": Ensure the JSON array in "Items (JSON Array)" is well-formed and matches the table schema.
- "Sort field not found": Confirm the "Sort By" field exists in the table schema.
- "Authentication failed": Check that the API key credential is correctly configured and valid.
Links and References
- n8n Expressions Documentation
- External API documentation for workspace, table, and row management (specific URL depends on the service used)