DinastiAPI Newsletter icon

DinastiAPI Newsletter

Manage WhatsApp newsletters/channels using DinastiAPI API

Actions15

Overview

The "Get Message Updates" operation of the DinastiAPI Newsletter node retrieves recent updates or new messages from a specified WhatsApp newsletter/channel. This is useful for workflows that need to monitor newsletters for new content, track message changes, or synchronize newsletter messages with other systems.

Practical examples include:

  • Automatically fetching new newsletter messages since a certain timestamp to trigger notifications or further processing.
  • Polling for message updates after a specific server ID to keep an external database in sync.
  • Limiting the number of retrieved updates to manage data volume and performance.

Properties

Name Meaning
Newsletter JID The unique identifier (JID) of the newsletter/channel to get message updates from.
Count Number of message updates to retrieve (limit).
Since Timestamp Unix timestamp to fetch updates starting from this time (optional).
After Server ID Fetch updates occurring after this specific server message ID (optional).

Output

The output JSON contains an array of message update objects returned by the API. Each object represents a newsletter message update with details such as message content, timestamps, sender info, and any metadata provided by the DinastiAPI service.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the DinastiAPI service managing WhatsApp newsletters.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The node uses HTTP POST requests to the /newsletter/message-updates endpoint of the DinastiAPI.

Troubleshooting

  • Common issues:

    • Invalid or missing Newsletter JID will cause the API request to fail.
    • Providing incorrect timestamp or server ID formats may result in empty or error responses.
    • Network or authentication errors if the API key is invalid or connectivity is lost.

  • Error messages:

    • Errors returned from the API are captured and can be output if "Continue On Fail" is enabled.
    • Typical errors include authorization failures, invalid parameters, or rate limiting.

  • Resolutions:

    • Verify the Newsletter JID is correct and corresponds to an existing newsletter.
    • Ensure timestamps and server IDs are valid numbers.
    • Check API credentials and network connectivity.
    • Use "Continue On Fail" to handle intermittent errors gracefully.

Links and References

Discussion