DinastiAPI Session icon

DinastiAPI Session

Manage WhatsApp session connections and configurations

Actions11

Overview

This node manages WhatsApp session connections and configurations via the DinastiAPI service. It allows users to connect or disconnect from WhatsApp servers, pair a phone number, configure proxy settings, manage storage options like S3, set up RabbitMQ messaging, and control various message skipping behaviors (e.g., skipping media, groups, newsletters, broadcasts, own messages, and calls).

A common use case is automating WhatsApp session management within an n8n workflow, such as establishing a connection to receive real-time WhatsApp events, configuring storage for media files, or setting up message filtering rules.

For example, you can use the Connect operation to subscribe to specific WhatsApp events (like messages or presence updates) and decide whether to wait for the connection to establish before proceeding. Another practical scenario is configuring S3 storage to handle media files received through WhatsApp.

Properties

Name Meaning
Events to Subscribe Select which WhatsApp events to listen for when connecting. Options include: All, Call, Chat Presence, Connected, Disconnected, Group Info, History Sync, Message, Presence, Push Name, QR Code, Read Receipt. Default is "All".
Immediate Connection Boolean flag indicating whether the node should return immediately after initiating connection (true), or wait until the connection is fully established (false).

Output

The node outputs JSON data representing the response from the DinastiAPI service for the requested operation. The structure varies depending on the operation performed but generally includes status information, session details, or configuration results.

  • For the Connect operation, the output contains confirmation of the connection attempt and subscribed events.
  • Other operations return relevant session or configuration data.
  • The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the DinastiAPI service.
  • The node interacts with the DinastiAPI endpoints over HTTP(S).
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Connection failures: Ensure the API key credential is valid and the DinastiAPI service is reachable.
  • Invalid event subscription: Selecting unsupported event names may cause errors; use only the provided event options.
  • Proxy misconfiguration: When setting proxy settings, ensure the proxy URL format is correct (e.g., socks5://user:pass@host:port).
  • S3 or RabbitMQ configuration errors: Verify all required fields (access keys, URLs, etc.) are correctly filled.
  • Timeouts on immediate connection: If Immediate Connection is set to false, the node waits for connection establishment, which might delay execution; set it to true to avoid waiting.

Common error messages typically relate to invalid parameters or authentication issues. Review the node's input parameters and credentials if errors occur.

Links and References

Discussion