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 interacts with the Messaging resource of the Appwrite API, specifically supporting the operation to list message logs for a given message. This operation retrieves logs related to a specific message ID, which can be useful for tracking delivery status, debugging issues, or auditing message history.
Common scenarios where this node is beneficial include:
- Monitoring the delivery and status of sent messages (email, push notifications, SMS).
- Auditing message activity for compliance or troubleshooting.
- Integrating message log retrieval into automated workflows for reporting or alerting.
For example, after sending an email campaign, you could use this node to fetch logs about each message's delivery attempts, failures, or successes.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the message whose logs you want to retrieve. |
| Additional Fields | Not applicable for this operation (no additional fields used in listing message logs). |
Note: Although the provided properties JSON includes multiple "Additional Fields" collections, for the List Message Logs operation only the Message ID parameter is required and used.
Output
The output is a JSON array containing the message logs associated with the specified Message ID. Each item in the array represents a log entry detailing events related to that message, such as delivery attempts, errors, timestamps, and statuses.
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the Appwrite API via an API key credential configured in n8n.
- The node uses the Appwrite SDK client internally to communicate with the messaging endpoints.
- Proper permissions on the Appwrite project are necessary to access messaging logs.
Troubleshooting
- Invalid Message ID: If the provided Message ID does not exist or is malformed, the node may return an error indicating the message was not found. Verify the Message ID is correct.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access messaging resources.
- Network Issues: Connectivity problems with the Appwrite server will cause request failures; check network settings and endpoint URL.
- Empty Results: If no logs are returned, confirm that the message has generated logs and that the Message ID is correct.