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 node integrates with the Appwrite platform to manage messaging services. Specifically, the "Update SMS" operation allows users to update an existing SMS message by modifying its content and related metadata such as recipients and scheduling.
This node is beneficial in scenarios where automated workflows need to modify SMS messages after creation, for example:
- Correcting or updating the text of a scheduled SMS before it is sent.
- Changing the list of recipients or scheduling time dynamically based on workflow conditions.
- Managing SMS campaigns by updating drafts or rescheduling messages.
Practical example: A marketing automation workflow creates an SMS campaign draft and later updates the message content and scheduled send time based on user input or external triggers.
Properties
| Name | Meaning |
|---|---|
| Message ID | Unique identifier of the SMS message to update. Can be generated automatically or provided manually. |
| Content | The new text content of the SMS message. |
| Additional Fields | Optional fields to further customize the SMS message: |
| - Topics | Comma-separated list of topic IDs associated with the message. |
| - Users | Comma-separated list of user IDs to target. |
| - Targets | Comma-separated list of target IDs (recipients). |
| - Draft | Boolean indicating if the message is a draft (true) or ready to send (false). |
| - Scheduled At | ISO 8601 formatted string specifying when the message should be sent. |
Output
The node outputs a JSON object representing the updated SMS message as returned by the Appwrite API. This typically includes details such as the message ID, content, status, recipients, scheduling information, and other 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 resources.
Troubleshooting
Common issues:
- Invalid or missing Message ID will cause the update to fail.
- Incorrectly formatted "Scheduled At" timestamps may result in errors or ignored scheduling.
- Insufficient permissions on the API key can lead to authorization errors.
- Providing invalid or empty content might cause the API to reject the update.
Error messages and resolutions:
- "Message not found" — Verify that the Message ID exists and is correct.
- "Unauthorized" — Check API key permissions and ensure credentials are valid.
- "Invalid date format" — Ensure "Scheduled At" uses proper ISO 8601 format.
- "Content required" — Make sure the content field is not empty.