Connect iPaaS provides one trigger for RabbitMQ. The RabbitMQ trigger on Connect iPaaS is a real time trigger. As soon as you receive a message on RabbitMQ Exchange, Connect iPaaS will be notified of it and it will perform action according to your workflow.
New Message ReceivedFigure 1. Trigger for RabbitMQ Application on Connect iPaaS
New Message Received¶
It triggers your workflow when a new message is published to your exchange. You can specify the exchange you want to listen to using Connect iPaaS.
Set up Trigger for your Workflow¶
When you select the
New Message Received trigger for RabbitMQ. You have to specify the following parameters:
Name of your RabbitMQ Exchange to which Connect iPaaS will listen. It should be an existing exchange.
Connect iPaaS will receive all the messages with this binding key. Binding key can be left blank in case of Fanout Exchange. The Binding key can also be left blank if you are providing your own queue which is already bound to the above mentioned exchange.
Connect iPaaS will create a queue with a default name (Conect-flowid) which will listen to messages with above specified binding key. If you want to use a pre existing queue or you want Connect iPaaS to create a queue with some other name, you can replace the default value in the field.
Define Custom Headers¶
On RabbitMQ trigger, you can define the headers for the incoming message. For example, in figure 3. The incoming message can have header fields
AppName of type String and
AppVersion of type integer.
The value of these headers will be available in Event Filtering and Conditionals. Also the value of these headers can be mapped to any Action application using Data Mapping.