DinastiAPI Newsletter icon

DinastiAPI Newsletter

Manage WhatsApp newsletters/channels using DinastiAPI API

Overview

This node integrates with the DinastiAPI to manage WhatsApp newsletters (channels). It allows users to perform various newsletter-related operations such as listing newsletters, creating new ones, subscribing/unsubscribing, sending messages, retrieving messages, reacting to messages, and more.

The Get Newsletter Messages operation specifically retrieves messages from a specified newsletter. This is useful for scenarios where you want to fetch recent or historical newsletter content programmatically, for example:

  • Archiving newsletter messages.
  • Displaying newsletter content in custom dashboards.
  • Processing newsletter messages for analytics or automation workflows.

Properties

Name Meaning
Newsletter JID The unique identifier (JID) of the newsletter from which to retrieve messages.
Count Number of messages to retrieve. Defaults to 25 if not specified.
Before Message ID Optional. Retrieve messages sent before this specific message server ID (for pagination).

Output

The output is a JSON array containing the retrieved newsletter messages. Each item corresponds to a message object returned by the DinastiAPI. The exact structure depends on the API response but typically includes message content, sender info, timestamps, and metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the DinastiAPI service.
  • The node makes HTTP requests to DinastiAPI endpoints to perform actions.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing newsletter JID will cause errors when fetching messages.
    • Requesting too many messages at once may lead to rate limiting or timeouts.
    • Using an incorrect "Before Message ID" that does not exist or is malformed can result in empty responses or errors.
  • Error messages:

    • Errors from the API are returned as error messages in the output JSON if "Continue On Fail" is enabled.
    • Authentication failures indicate invalid or missing API credentials.
    • Validation errors occur if required parameters like "Newsletter JID" are missing.
  • Resolutions:

    • Verify the newsletter JID is correct and corresponds to an existing newsletter.
    • Use reasonable values for "Count" to avoid overloading the API.
    • Ensure the API key credential is correctly set up and has proper permissions.

Links and References

Discussion