Actions84
- Avatar Actions
- Document Actions
- Function Actions
- Messaging Actions
- Create APNS Provider
- Create Email
- Create FCM Provider
- Create Mailgun Provider
- Create MSG91 Provider
- Create Provider
- Create Push
- Create Sendgrid Provider
- Create SMS
- Create SMTP Provider
- Create Subscriber
- Create Telesign Provider
- Create Textmagic Provider
- Create Topic
- Create Twilio Provider
- Create Vonage Provider
- Delete Provider
- Delete Subscriber
- Delete Topic
- Get Message
- Get Provider
- Get Subscriber
- Get Topic
- List Message Logs
- List Messages
- List Provider Logs
- List Providers
- List Subscriber Logs
- List Subscribers
- List Targets
- List Topic Logs
- List Topics
- Update APNS Provider
- Update Email
- Update FCM Provider
- Update Mailgun Provider
- Update MSG91 Provider
- Update Provider
- Update Push
- Update Sendgrid Provider
- Update SMS
- Update SMTP Provider
- Update Telesign Provider
- Update Textmagic Provider
- Update Topic
- Update Twilio Provider
- Update Vonage Provider
- Storage Actions
- Token Actions
- Users Actions
Overview
This node integrates with Appwrite's Storage service to manage files and buckets. Specifically, the "Create File" operation allows users to upload a new file into a specified storage bucket within their Appwrite project. This is useful for automating file uploads in workflows, such as saving user-generated content, backing up data, or processing files before further automation steps.
Practical examples:
- Uploading images or documents collected from form submissions directly into an Appwrite storage bucket.
- Automating backups of generated reports by creating files in cloud storage.
- Storing logs or exported data files dynamically during workflow execution.
Properties
| Name | Meaning |
|---|---|
| Bucket ID | The identifier of the storage bucket where the file will be uploaded. |
| File Name | The name to assign to the newly created file in the bucket. |
| File | The actual file content to upload. |
| Mime Type | The MIME type of the file being uploaded (e.g., image/png, application/pdf). |
Output
The output JSON contains the response from the Appwrite API after creating the file. This typically includes metadata about the uploaded file such as its unique ID, bucket ID, file name, size, MIME type, creation date, and any other relevant attributes returned by Appwrite.
If the node supports binary data output (not explicitly shown here), it would represent the uploaded file or related binary content, but in this case, the output focuses on JSON metadata describing the stored file.
Dependencies
- Requires an active Appwrite project with Storage service enabled.
- Needs credentials containing the Appwrite endpoint URL, project ID, and an API key with permissions to create files in storage buckets.
- Uses the official Appwrite SDK (
node-appwrite) to interact with the Appwrite API.
Troubleshooting
- Invalid Bucket ID: If the bucket ID does not exist or is incorrect, the API call will fail. Verify the bucket ID is correct and accessible.
- File Content Issues: The "File" property must contain valid file data. Ensure the input is correctly formatted and not empty.
- MIME Type Mismatch: Providing an incorrect MIME type may cause issues with how the file is handled or displayed. Use standard MIME types.
- Authentication Errors: Ensure the API key credential has sufficient permissions and is correctly configured.
- Large Files: Uploading very large files might hit size limits or timeouts; check Appwrite bucket settings and n8n timeout configurations.
Common error messages usually relate to authentication failures, missing parameters, or invalid bucket/file IDs. Resolving them involves checking credentials, input parameters, and Appwrite project configuration.