Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
The "Query Records" operation of the "Records" resource allows users to retrieve paginated records from a specified collection in Cogfy Tables. This node is useful when you want to fetch data entries stored in a particular collection, with options to control pagination, sorting, and filtering of the results.
Common scenarios include:
- Retrieving a specific page of records for display or processing.
- Applying complex filters to extract only records matching certain criteria.
- Sorting records by one or more fields in ascending or descending order.
For example, you might use this node to get the first 50 customer records sorted by their signup date, or to query all records where the status field equals "active".
Properties
| Name | Meaning |
|---|---|
| Collection Id | The unique identifier of the collection from which to query records. |
| Page Number | The page number to retrieve, starting at 0. Defaults to 0 (the first page). |
| Page Size | The number of records to return per page. Defaults to 50. |
| Order By | JSON array specifying fields and directions to sort the results by. Example: |
| ```json | |
| [ | |
| { "fieldId": "createdAt", "direction": "desc" } | |
| ] | |
| Filter | JSON object defining filter conditions for the query using logical operators like "and". |
| Example: | |
| ```json | |
| { | |
| "and": { | |
| "filters": { | |
| "status": { "eq": "active" } | |
| } | |
| } | |
| } | |
| ``` |
Output
The node outputs JSON data containing the queried records from the specified collection. Each item in the output corresponds to a record matching the query parameters, including any applied filters and sorting.
The structure typically includes:
- Record fields as key-value pairs.
- Metadata about the record if provided by the API.
This node does not output binary data.
Dependencies
- Requires an active connection to the Cogfy Tables API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the API must be set in the credential configuration.
Troubleshooting
- Empty Results: If no records are returned, verify that the collection ID is correct and that the filter conditions match existing records.
- Invalid JSON in Filter or Order By: Ensure that the JSON entered in the "Filter" and "Order By" properties is valid and correctly formatted.
- Authentication Errors: Confirm that the API key or token is valid and has sufficient permissions.
- Pagination Issues: Remember that page numbering starts at 0; requesting a page number beyond available pages will result in empty responses.
Links and References
- Cogfy Tables API Documentation (example placeholder link)
- n8n Documentation on HTTP Request Nodes (for understanding API integrations)