Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
This node operation allows uploading a file to a specific field within a record in a collection managed by the Cogfy Tables API. It is useful when you want to programmatically attach files (such as images, documents, or other media) to records stored in a structured data collection.
Typical use cases include:
- Automatically attaching user-uploaded files to database records.
- Importing files from external sources and linking them to existing records.
- Managing document storage within a custom data management workflow.
Properties
| Name | Meaning |
|---|---|
| Collection Id | The identifier of the collection where the target record resides. |
| Field Id | The identifier of the field within the record that will hold the uploaded file. |
| Record Id | The identifier of the record to which the file will be attached. |
| File | JSON object containing the file information to upload. This typically includes file name, content, and possibly encoding details. |
Output
The node outputs JSON data representing the response from the Cogfy Tables API after the file upload operation. This usually contains metadata about the uploaded file, confirmation of success, or error details if the upload failed.
If the node supports binary data output (not explicitly shown here), it would represent the uploaded file's binary content or related file streams.
Dependencies
- Requires an API key credential for authenticating with the Cogfy Tables API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the
@amonlibanio/n8n-openapi-nodepackage for building request properties and handling API interactions. - The OpenAPI specification (
openapi.json) for Cogfy Tables is bundled and used internally to define available operations and parameters.
Troubleshooting
- Missing or invalid Collection Id, Field Id, or Record Id: Ensure these IDs are correct and correspond to existing entities in your Cogfy Tables environment.
- File property format errors: The file input must be a valid JSON object describing the file; malformed JSON or missing required fields can cause failures.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- API endpoint issues: Confirm the base URL is correct and the Cogfy Tables API service is reachable.
- Error messages from API: Typically include HTTP status codes and error descriptions; consult Cogfy Tables API documentation for detailed meanings.
Links and References
- Cogfy Tables API Documentation (hypothetical link as not provided)
- n8n Documentation - Creating Custom Nodes
- OpenAPI Specification