Streaming & Messaging · Integration
RabbitMQ
Add RabbitMQ to your product for your customers, and give your AI agents governed access to it.
RabbitMQ is a message broker, so nothing is addressed to a queue directly: a publisher sends to an exchange with a routing key, and the customer's own bindings decide which queues get a copy. That indirection is the feature, and it is also why an integration that hard-codes a queue name breaks the first time a platform team re-routes something. Delivery semantics are the other half. An unacknowledged message is redelivered, so a consumer has to be safe to run twice, and a queue with no dead-letter target quietly loses whatever keeps failing. Virtual hosts separate one tenant's topology from another's, and the management HTTP API is where queue depth, consumer counts and bindings are read. fastn holds each broker's credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own broker and virtual host so your product publishes into topology their platform team owns.
Publish to an exchange with a routing key and let the customer's bindings decide where it lands, instead of naming a queue in your code.
Consume a queue and acknowledge only once the work succeeded, treating redelivery as normal rather than as an error to page on.
Read queue depth and consumer counts from the management API so your product can show a backlog before somebody notices it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which queues are backing up and how deep they are, scoped to one customer's virtual host.
An agent publishes an approved message within scoped permissions, with the exchange and routing key logged.
An agent inspects bindings to explain where a published message would actually be delivered.
Example prompt
Which queues on this vhost have a growing backlog, and how many consumers are attached to each?
Set up RabbitMQ in 4 steps
- 01Enable the RabbitMQ connector in your fastn dashboard.
- 02Have each customer supply their own broker connection and virtual host, so publishes and consumes run under their credentials.
- 03Map the exchanges, routing keys and queues your product uses, and decide what a redelivered or dead-lettered message should mean.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the RabbitMQ integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a RabbitMQ integration without building it. Your customers connect their own RabbitMQ account inside your product and work their topics, streams and messages there, with no per-customer code on your side.
- Handle the part that actually costs time: ordering and replay are the whole problem: a consumer that falls behind must be able to resume without losing or double-processing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a RabbitMQ update is not your on-call problem.
- One integration serves your product and your agents. The same governed RabbitMQ connection powers in-product features and gives AI agents scoped, audited access, so you move events between your product and your customers' systems without either side polling without wiring it twice.
Used by these teams
Compare with
Apache Kafka
Google Cloud Pub/Sub
Azure Service BusOften used alongside
Tools the same teams tend to run next to RabbitMQ, across other categories.
Snowflake
Airtable
PostgreSQL
Anthropic ClaudeRabbitMQ integration FAQ
How do I add a RabbitMQ integration to my product?
Enable the RabbitMQ connector in your fastn dashboard, then let each customer authenticate their own RabbitMQ account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no RabbitMQ client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own RabbitMQ account?
Yes. Every connection is scoped to the individual customer, so each authorises their own RabbitMQ account and only ever sees their own topics, streams and messages. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this RabbitMQ integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which queues are backing up and how deep they are, scoped to one customer's virtual host.
Who maintains the RabbitMQ integration?
fastn does. When RabbitMQ changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product replay RabbitMQ messages after an outage?
Yes, within the retention the customer's own RabbitMQ setup keeps. Consumer position is tracked per tenant, so a consumer that falls behind resumes from where it stopped rather than skipping ahead or starting over, which is the difference between a gap in your data and a duplicate in it.
How is one customer's stream kept separate from another's?
Each customer authorises their own RabbitMQ connection, so topics, credentials and consumer positions are theirs alone. That matters more here than in most integrations, because a misrouted message is delivered before anyone can review it.
What can I build with the RabbitMQ integration?
A common starting point: let each customer connect their own broker and virtual host so your product publishes into topology their platform team owns. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the RabbitMQ integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding RabbitMQ does not change your per-connector cost. You can start free with 3 connected accounts.
Add RabbitMQ to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.