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
The "Update Email" operation in the Messaging resource allows users to update an existing email message within the Appwrite platform. This node is useful when you need to modify details of a previously created email message, such as changing its subject, content, recipients, or scheduling information.
Common scenarios include:
- Editing the subject or body of an email before sending.
- Updating recipient lists (CC, BCC, targets, users, topics).
- Changing whether the email is a draft or scheduled for later delivery.
- Switching between plain text and HTML content formats.
For example, you might use this node to update a marketing email's content and schedule it for a new send time without creating a new message from scratch.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the email message to update. Can be generated randomly or provided. |
| Subject | The updated subject line of the email. |
| Content | The updated main content/body of the email message. |
| Additional Fields | A collection of optional fields to further customize the email: |
| - BCC | Comma-separated list of email addresses to blind carbon copy. |
| - CC | Comma-separated list of email addresses to carbon copy. |
| - Draft | Boolean indicating if the message should be saved as a draft (true) or not (false). |
| - Enabled | Boolean indicating whether the messaging provider is enabled. |
| - From Email | The sender's email address. |
| - From Name | The sender's display name. |
| - HTML | Boolean indicating if the email content is HTML formatted (true) or plain text (false). |
| - Scheduled At | ISO 8601 formatted string specifying when the email should be sent (for scheduling). |
| - Targets | Comma-separated list of target IDs to receive the email. |
| - Topics | Comma-separated list of topic IDs associated with the email. |
| - Users | Comma-separated list of user IDs to receive the email. |
Output
The node outputs a JSON object representing the updated email message as returned by the Appwrite API. This typically includes all properties of the email message such as its ID, subject, content, recipients, status (draft or sent), scheduling info, and metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Appwrite API via an API key credential configured in n8n.
- The node depends on the Appwrite SDK and relevant API endpoints for messaging.
- Proper permissions must be granted to the API key to update messaging emails.
Troubleshooting
- Invalid Message ID: If the provided Message ID does not exist, the node will throw an error indicating the message was not found. Verify the ID is correct.
- Missing Required Fields: Subject and content are required; omitting them may cause errors or incomplete updates.
- Invalid Date Format: The "Scheduled At" field must be in valid ISO 8601 format; otherwise, scheduling will fail.
- Permission Denied: Ensure the API key has sufficient rights to update messages.
- Malformed Recipient Lists: Comma-separated lists for CC, BCC, targets, topics, and users must be properly formatted without extra spaces or invalid characters.
To resolve errors, check input values carefully, confirm API credentials, and consult Appwrite API documentation for messaging constraints.