All templates
Integration#RabbitMQ#Queue#Events#Integration

RabbitMQ Delayed Publisher

Publish a release message to RabbitMQ with an optional delivery delay for downstream consumers.

RabbitMQ Delayed Publisher

Publish an operational event into RabbitMQ from a small Heym workflow. This template accepts a message body, sends it to an exchange with a routing key, and demonstrates delayed delivery with rabbitmqDelayMs.

What this workflow does

  1. Input accepts a release message from the caller
  2. RabbitMQ publishes that message to an exchange with a routing key
  3. Output returns the broker-generated message ID

Use cases

  • Delayed rollout events
  • Queue-based handoff to downstream workers
  • Operational notifications for release systems

Setup

Create a RabbitMQ credential in Heym, then update the exchange and routing key to match your broker topology. Remove rabbitmqDelayMs if your broker does not support delayed messages.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3Press Cmd+V / Ctrl+V — nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
#RabbitMQ#Queue#Events#Integration

Click a node to select it — same as the Heym editor; the panel shows its settings.

4 nodes · Free & source-available

Explore related automations — each page links to other templates so you can discover more use cases.

Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym