ZuckZapGo Newsletter icon

ZuckZapGo Newsletter

Manage WhatsApp newsletters/channels using ZuckZapGo API
Join our community

Actions15

Overview

The "Mark Newsletter Viewed" operation in the ZuckZapGo Newsletter node allows users to mark specific newsletter messages as viewed/read. This is useful for managing message states within WhatsApp newsletters or channels, ensuring that certain messages are acknowledged and not repeatedly processed or notified.

Typical use cases include:

  • Automatically marking a batch of newsletter messages as read after processing them.
  • Synchronizing message read status between different systems or user interfaces.
  • Managing notification states to avoid redundant alerts for already seen content.

For example, if you receive multiple newsletter messages identified by their server IDs, you can mark all those messages as viewed in one API call, helping keep your message tracking consistent.

Properties

Name Meaning
Newsletter JID The unique identifier (JID) of the newsletter whose messages you want to mark as viewed.
Server IDs A comma-separated list of server message IDs that you want to mark as viewed.

Output

The output is a JSON array containing the response from the API after marking the specified messages as viewed. It typically includes confirmation details or status information about the operation's success.

No binary data is output by this operation.

Example output structure (simplified):

[
  {
    "status": "success",
    "markedServerIds": [123, 456, 789]
  }
]

Dependencies

  • Requires an active connection to the ZuckZapGo API service.
  • Requires an API key credential configured in n8n for authenticating requests to the ZuckZapGo API.
  • The node uses HTTP POST requests to the /newsletter/mark-viewed endpoint of the ZuckZapGo API.

Troubleshooting

  • Invalid or missing Newsletter JID: Ensure the Newsletter JID is correctly provided and corresponds to an existing newsletter.
  • Malformed Server IDs: The Server IDs must be a comma-separated string of numeric IDs. Non-numeric or improperly formatted IDs will cause errors.
  • API authentication errors: Verify that the API key credential is valid and has the necessary permissions.
  • Network or connectivity issues: Check network access to the ZuckZapGo API endpoint.
  • Error messages from API: The node returns error messages from the API in the output if continueOnFail is enabled; otherwise, it throws exceptions. Review these messages for specific causes.

Links and References

Discussion