Actions11
Overview
This node manages WhatsApp session connections and configurations, specifically allowing users to configure RabbitMQ settings for event publishing related to WhatsApp sessions. It is useful in scenarios where you want to integrate WhatsApp events with a message broker system like RabbitMQ to enable asynchronous processing, event-driven workflows, or real-time notifications.
For example, you can configure the node to publish WhatsApp message events or read receipts to a RabbitMQ exchange, which downstream services can consume for analytics, logging, or triggering other automated processes.
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; options: Topic, Direct, Fanout, Headers |
| Queue | Name of the RabbitMQ queue (auto-generated if empty) |
| Queue Type | Type of queue to create; options: Classic, Quorum, Stream |
| Routing Key | Routing key pattern for binding messages |
| 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; options: Non-Persistent (1), Persistent (2) |
Output
The node outputs JSON data representing the response from the WhatsApp session API after configuring RabbitMQ settings. The output structure corresponds to the API's response format, typically confirming the success or failure of the configuration operation.
No binary data output is involved.
Dependencies
- Requires an active WhatsApp session API credential (an API key or token) configured in n8n.
- Needs access to the RabbitMQ server specified by the connection URL.
- The node uses internal API endpoints to send configuration commands to the WhatsApp session management backend.
Troubleshooting
- Connection Errors: If the node cannot connect to RabbitMQ, verify the connection URL, credentials, and network accessibility.
- Invalid Configuration: Ensure that required fields such as
url,exchange_type, andqueue_typeare correctly set. - Permission Issues: The RabbitMQ user must have permissions to declare exchanges and queues as per the configuration.
- API Errors: Errors returned from the WhatsApp session API will be surfaced; check the error message for details and ensure the API credentials are valid.
- Empty Fields: Leaving
exchangeorqueueempty will auto-generate names, but if specific names are required, provide them explicitly.
Links and References
- RabbitMQ Official Documentation
- AMQP 0-9-1 Model Explained
- WhatsApp Business API - Event Webhooks (for context on events)