DinastiAPI Chat icon

DinastiAPI Chat

Perform chat operations with DinastiAPI WhatsApp API

Actions6

Overview

This node integrates with the DinastiAPI WhatsApp API to perform various chat-related operations. Specifically, the "Mark as Read" operation allows users to mark one or more messages in a specified chat as read. This is useful for automating message status updates, ensuring that messages are acknowledged without manual intervention.

Practical scenarios include:

  • Automatically marking incoming messages as read after processing them.
  • Synchronizing message read status across multiple systems or devices.
  • Managing message states in customer support workflows to track which messages have been seen.

Properties

Name Meaning
Message IDs Comma-separated list of message IDs to mark as read (e.g., AABBCC11223344,DDEEFF55667788). These identify the specific messages to update.
Chat JID The unique identifier (Jabber ID) of the chat containing the messages (e.g., 5491155553934.0:1@s.whatsapp.net). Specifies the chat context.
Sender JID (Optional) The unique identifier of the message sender (e.g., 5491155553111.0:1@s.whatsapp.net). Used to filter or specify messages from a particular sender.

Output

The node outputs JSON data representing the response from the DinastiAPI WhatsApp API after attempting to mark the messages as read. The structure typically includes confirmation of the operation's success or details about any errors encountered.

No binary data output is produced by this operation.

Example output JSON structure (simplified):

{
  "success": true,
  "markedMessages": [
    "AABBCC11223344",
    "DDEEFF55667788"
  ]
}

Dependencies

  • Requires an active connection to the DinastiAPI WhatsApp API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The node uses the /chat/markread endpoint of the DinastiAPI.

Troubleshooting

  • Common Issues:

    • Invalid or malformed message IDs can cause the API request to fail.
    • Incorrect Chat JID format may result in no messages being marked.
    • Missing required parameters (messageIds or chatJid) will prevent execution.

  • Error Messages:

    • Errors returned from the API will be included in the node output if "Continue on Fail" is enabled.
    • Typical error messages might indicate authentication failure, invalid IDs, or permission issues.

  • Resolution Tips:

    • Verify that message IDs are correctly formatted and exist in the specified chat.
    • Ensure the Chat JID matches the target chat exactly.
    • Confirm that the API key credential is valid and has necessary permissions.

Links and References

Discussion