Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
This node interacts with the Cogfy Tables API to retrieve detailed information about a specific collection. It is useful when you need to fetch metadata or data structure details of a collection stored in Cogfy Tables, such as its fields, records, or configuration. Practical examples include dynamically loading collection schemas for further processing, validating collection existence before operations, or displaying collection details in workflows.
Properties
| Name | Meaning |
|---|---|
| Collection Id | The unique identifier of the collection to retrieve. This is a required string input specifying which collection's details to fetch. |
Output
The node outputs JSON data representing the full details of the specified collection. This typically includes metadata such as collection name, fields, records, and other configuration details as provided by the Cogfy Tables API. There is no binary output.
Dependencies
- Requires an active connection to the Cogfy Tables API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the API must be set in the credentials configuration.
Troubleshooting
- Invalid Collection Id: If the provided Collection Id does not exist or is malformed, the node will likely return an error indicating the collection was not found. Verify the Collection Id is correct.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly configured.
- Network Issues: Connectivity problems to the Cogfy Tables API endpoint can cause request failures. Check network access and base URL correctness.
- API Rate Limits: Excessive requests may trigger rate limiting errors from the API. Implement retry logic or reduce request frequency if needed.
Links and References
- Cogfy Tables API Documentation (example link, replace with actual)
- n8n documentation on Using API Credentials