RabbitMQ
AMQP 0-9-1 message broker client for RabbitMQ. Provides connection management, message publishing (to queues or exchanges with routing keys, content types, delivery modes, priority, and TTL), single-message consumption with optional JSON parsing and auto-acknowledgment, queue management (declare, delete, bind, purge), and exchange management (declare with direct/fanout/topic/headers types, delete). Supports both explicit Connect/Disconnect lifecycle and implicit per-node credential-based connections. Authenticates via host, port, username, password, and virtual host credentials.
| Namespace | Robomotion.RabbitMQ |
| Version | 1.1.0 |
| Category | Communication, Dev Tools |
| Nodes | 11 |
Nodes
| Node | Description |
|---|---|
| Connect | Opens a connection to RabbitMQ and returns a Client ID. |
| Disconnect | Closes a RabbitMQ connection. |
| Publish | Publishes in RabbitMQ. |
| Consume | Consume — see the properties below. |
| Declare Queue | Declare Queue — see the properties below. |
| Delete Queue | Deletes a queue in RabbitMQ. |
| Purge Queue | Purge Queue — see the properties below. |
| Bind Queue | Bind Queue — see the properties below. |
| Declare Exchange | Declare Exchange — see the properties below. |
| Delete Exchange | Deletes an exchange in RabbitMQ. |
| Toolkit | Exposes this package's operations to an AI Agent as a single tool. |
Connecting
This package has a Connect node. Run it once at the start of your flow; it returns a Client ID that the other nodes take as input. Pair it with Disconnect so the connection is released when the flow ends.
Credentials belong in a Vault rather than typed into the node.
AI Agent tools
10 of these nodes are exposed as tools an AI Agent can call directly:
Connect, Disconnect, Publish, Consume, Declare Queue, Delete Queue, Purge Queue, Bind Queue, Declare Exchange, Delete Exchange.
Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.
It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.