Actions11
Overview
This node manages WhatsApp session connections and configurations via a DinastiAPI service. It supports various operations including connecting, disconnecting, logging out, pairing a phone, configuring proxy settings, and managing integrations with external services like RabbitMQ and S3 storage. The "Configure RabbitMQ" operation specifically allows users to set up RabbitMQ messaging parameters for publishing WhatsApp events.
Typical use cases include:
- Automating WhatsApp session management in workflows.
- Configuring RabbitMQ to publish WhatsApp event messages for real-time processing or integration with other systems.
- Adjusting message delivery modes, queue types, and exchange settings to fit messaging infrastructure needs.
For example, a user can enable RabbitMQ publishing to send all WhatsApp message events to a specific exchange and queue, facilitating downstream processing or analytics.
Properties
| Name | Meaning |
|---|---|
| Enable RabbitMQ | Whether to enable RabbitMQ publishing |
| URL | RabbitMQ connection URL (e.g., amqp://user:pass@host:port/vhost) |
| Exchange | Name of the RabbitMQ exchange (auto-generated if empty) |
| Exchange Type | Type of exchange to create: Topic, Direct, Fanout, Headers |
| Queue | Name of the RabbitMQ queue (auto-generated if empty) |
| Queue Type | Type of queue to create: Classic, Quorum, Stream |
| Routing Key | Routing key pattern for message routing (e.g., events.#) |
| Events | Events to publish, either "All" or comma-separated list like "Message,ReadReceipt" |
| Durable | Whether the exchange/queue should survive server restarts |
| Auto Delete | Whether to auto-delete the queue/exchange when unused |
| Exclusive | Whether the queue is exclusive to this connection |
| No Wait | Whether to wait for server confirmation |
| Delivery Mode | Message delivery mode: Non-Persistent (1), Persistent (2) |
Output
The node outputs JSON data representing the response from the DinastiAPI service for the requested operation. For the "Configure RabbitMQ" operation, the output typically includes confirmation or details of the applied RabbitMQ configuration.
The output JSON structure corresponds directly to the API response and is wrapped as an array of items for n8n workflow compatibility.
No binary data output is produced by this node.
Dependencies
- Requires access to the DinastiAPI service managing WhatsApp sessions.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- For RabbitMQ configuration, requires a valid RabbitMQ connection URL with appropriate permissions.
- No additional environment variables are explicitly required beyond standard API credential setup.
Troubleshooting
- Connection Errors: If the RabbitMQ URL is incorrect or unreachable, the node will fail to configure RabbitMQ. Verify the URL format and network accessibility.
- Permission Issues: Insufficient permissions on the RabbitMQ server may cause failures. Ensure the provided credentials have rights to create exchanges and queues.
- Invalid Parameters: Providing unsupported exchange types, queue types, or malformed routing keys can cause errors. Use only supported options as listed in properties.
- API Request Failures: Network issues or invalid API credentials will result in request errors. Check API key validity and network connectivity.
- Empty Required Fields: Required fields like the RabbitMQ URL must not be empty; otherwise, the operation will fail.
Error messages returned by the API generally indicate the nature of the problem (e.g., authentication failure, invalid parameter). Review these messages and adjust configuration accordingly.
Links and References
- RabbitMQ Official Documentation
- AMQP URI Format
- DinastiAPI WhatsApp Session Management (if publicly available) (Replace with actual link if available)