Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
The node interacts with the Cogfy Tables API to list records from a specified collection. It is useful when you want to retrieve paginated data entries stored in a particular collection within Cogfy Tables. Common scenarios include fetching batches of records for processing, reporting, or integration with other systems.
For example, you might use this node to:
- Retrieve the first 10 records from a customer database collection.
- Paginate through large datasets by specifying different page numbers and sizes.
- Integrate record data into workflows that require batch processing or conditional logic based on record contents.
Properties
| Name | Meaning |
|---|---|
| Collection Id | The unique identifier of the collection from which to list records. |
| Page Number | The page number to retrieve, starting at 0. Defaults to 0 (the first page). |
| Page Size | The number of results per page. Defaults to 10. Controls how many records are returned. |
Output
The node outputs JSON data representing the list of records retrieved from the specified collection. Each item in the output corresponds to a record object as returned by the Cogfy Tables API. The structure typically includes fields and values defined in the collection schema.
If the API supports binary data associated with records, it would be included accordingly, but based on the provided code and properties, the primary output is JSON-formatted record data.
Dependencies
- Requires an API key credential for authenticating with the Cogfy Tables API.
- Needs the base URL of the Cogfy Tables API configured in the credentials.
- Depends on the
@amonlibanio/n8n-openapi-nodepackage for OpenAPI integration. - Uses an OpenAPI specification (
openapi.json) bundled with the node for request building.
Troubleshooting
- Invalid Collection Id: If the collection ID is incorrect or does not exist, the API will likely return an error or empty result. Verify the collection ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node credentials.
- Pagination Issues: Requesting a page number beyond the available range may return empty results. Adjust the page number accordingly.
- Network or API Downtime: Connectivity issues or API service interruptions can cause request failures. Check network connectivity and Cogfy Tables service status.
Links and References
- Cogfy Tables API Documentation (example placeholder, replace with actual if available)
- n8n OpenAPI Node Integration Guide