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 "Get Subscriber" operation. This operation retrieves detailed information about a subscriber associated with a particular messaging topic.
This node is beneficial in scenarios where you need to manage or audit subscribers of messaging topics within Appwrite, such as verifying subscriber details before sending notifications or managing subscription lists programmatically.
Example use case:
You have a messaging topic for product updates and want to fetch details about a specific subscriber to check their subscription status or metadata before sending targeted messages.
Properties
| Name | Meaning |
|---|---|
| Topic ID | The unique identifier of the messaging topic to which the subscriber belongs. |
| Subscriber ID | The unique identifier of the subscriber whose details you want to retrieve. |
| Additional Fields | (Not applicable for this operation; included in the general properties but not used here.) |
Output
The output is a JSON object containing the subscriber's details as returned by the Appwrite Messaging API. This typically includes subscriber identifiers, target IDs, and any metadata associated with the subscriber.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Appwrite API via an API key credential.
- The node expects valid credentials including the Appwrite endpoint URL, project ID, and an API key.
- No additional environment variables are required beyond the configured credentials.
Troubleshooting
Common issues:
- Invalid or missing Topic ID or Subscriber ID parameters will cause the API call to fail.
- Network connectivity problems or incorrect API credentials can result in authentication errors.
- If the subscriber does not exist under the specified topic, the API will return an error indicating the subscriber was not found.
Error messages and resolutions:
"Resource not found": Verify that both the Topic ID and Subscriber ID are correct and that the subscriber exists.- Authentication errors: Check that the API key and project ID credentials are correctly configured.
- Timeout or network errors: Ensure the Appwrite server is reachable from your n8n instance.