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 the Appwrite API to create a file access token for a specific file stored in an Appwrite storage bucket. The "Create File Token" operation generates a temporary token that can be used to securely access or share a file without exposing permanent credentials.
Common scenarios:
- Generating a time-limited URL or token to allow external users or systems to download or access a file.
- Automating secure file sharing workflows where direct file access needs to be controlled and limited by expiry.
- Integrating with other systems that require a token-based authentication to fetch files from Appwrite storage.
Practical example:
You have a file stored in an Appwrite bucket containing sensitive reports. You want to send a link to a client that expires after 24 hours. Using this node, you create a file token with an expiry date set 24 hours ahead, then provide the token to the client for secure access.
Properties
| Name | Meaning |
|---|---|
| Bucket ID | Unique identifier of the storage bucket where the file is located. |
| File ID | Unique identifier of the file for which the token will be created. |
| Expire | Optional ISO 8601 formatted date/time string specifying when the token should expire. |
Output
The output JSON contains the response from the Appwrite API representing the created file token object. This typically includes:
- The token string itself (used for accessing the file).
- Metadata such as creation time, expiry time (if set), and associated file and bucket IDs.
No binary data is output by this operation; it strictly returns JSON metadata about the token.
Dependencies
- Requires an active connection to an Appwrite server via its REST API.
- Needs an API key credential configured in n8n to authenticate requests to Appwrite.
- The Appwrite Storage service must be enabled and properly configured with buckets and files.
Troubleshooting
- Invalid Bucket ID or File ID: If either ID does not exist or is incorrect, the API will return an error. Verify the IDs are correct and that the file exists in the specified bucket.
- Expired or Malformed Expiry Date: If the
Expireproperty is provided but not in valid ISO 8601 format, the request may fail. Ensure the expiry date string is correctly formatted. - Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm the API key credential is valid and has sufficient permissions.
- Permission Denied: The API user must have permission to generate tokens for the specified bucket and file.
- Network Issues: Connectivity problems with the Appwrite server will result in errors. Check network access and server availability.