Maytapi icon

Maytapi

Integrate with Maytapi WhatsApp Unofficial API

Actions55

Queue → Get Queue

AI-generated

Overview

This node integrates with the Maytapi WhatsApp Unofficial API, enabling automation and interaction with WhatsApp accounts through various resources such as messages, contacts, chats, groups, queues, calls, sessions, and account management. Specifically, for the Queue resource with the Get Queue operation, it retrieves the message queue associated with a specific WhatsApp phone instance.

Use cases include monitoring pending or queued messages for a WhatsApp phone number managed via Maytapi, which can be useful for troubleshooting message delivery issues, analyzing message flow, or integrating queue status into broader workflows.

Example scenario: You want to check if there are any unsent or pending messages in your WhatsApp instance's queue before sending new messages or triggering alerts.

Properties

Name Meaning
Phone ID Source Select how to provide the Phone ID of the WhatsApp instance: either from credentials or custom input.
Phone ID (Required if "Custom" is selected) The custom Phone ID string identifying the WhatsApp instance whose queue you want to get.

Output

The output is a JSON object representing the current message queue for the specified WhatsApp phone instance. The exact structure depends on the Maytapi API response but typically includes details about queued messages such as message IDs, content, timestamps, and statuses.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for Maytapi WhatsApp API access.
  • The node uses the Maytapi API base URL https://api.maytapi.com/api.
  • The Phone ID must be provided either via credentials or as a custom input property.
  • Proper network connectivity to Maytapi API endpoints is necessary.

Troubleshooting

  • Missing Phone ID Error: If neither credentials nor custom Phone ID is provided, the node throws an error stating "Phone ID is required." Ensure you have set the Phone ID correctly.
  • API Request Failures: Network issues or invalid API keys will cause request failures. Verify your API key credential and internet connection.
  • Unsupported Operation: Using an unsupported operation or resource combination will throw an error. Confirm that you have selected "Queue" as resource and "Get Queue" as operation.
  • Empty Queue Response: An empty JSON response may indicate no messages are currently queued.

Links and References

Discussion