Skip to content

RabbitMQ Actions

Actions are the operations (or API operations) that you can perform on RabbitMQ by a simple drag and drop and data mapping of elements and values from the input trigger, derived values using formulas or desired constant that you may wish to map.

The Publish Message action on RabbitMQ automates sending on messages using RabbitMQ.

As shown in figure 1., you can Publish Messages to the RabbitMQ exchange in response to a trigger event.

Action for RabbitMQ Application on Connect iPaaS

Figure 1. Action for RabbitMQ Application on Connect iPaaS

Set up RabbitMQ action in your workflow

After selecting the action "Publish Message" as shown in the above figure, you can continue to configure or set up your action parameter that will define what message will be published in RabbitMQ exchange. You can also construct the content of the message being published or other properties using values from the input trigger event. You can also select other attributes of the message. Additionally, you can add custom message headers ot the outgoing message.

To populate your outgoing message and other message properties, you can use excel style functions and sophisticated Data Mapping and Transformation capabilities on Connect iPaaS. Setting up RabbitMQ Action

Figure 2. Setting up RabbitMQ action on Connect iPaaS

Exchange Name

Name of the Exchange to which the outgoing message will be published to.

Routing key

Routing key of the outgoing message.


Payload of the outgoing message.

Optional Properties

Along with these you can add multiple optional properties to the outgoing message:

  • Priority - The priority of AMQP message
  • Character Encoding Type - The character encoding of AMQP message
  • Content Type - Content type, e.g. "application/json". Used by applications, not core RabbitMQ.
  • Correlation Id - Helps correlate requests with responses. See More
  • Reply To - Carries response queue name. See More
  • Expiration - Per-message TTL
  • Message Id - Arbitrary message ID
  • Type - Application-specific message type, e.g. "orders.created"
  • User Id - User ID. See More
  • App Id - Application Name
  • Cluster Id - Cluster Id
  • Timestamp - Application-provided timestamp
  • Custom Headers - You can add custom headers to the outgoing message.

Custom Headers

You can also add custom headers in your outgoing message. For example in Figure 3. We are adding App Name and App Version headers to the message.

Custom headers in outgoing message on RabbitMQ

Figure 3. Custom headers in outgoing message on RabbitMQ