Checklist ✅

• The issue is present in the latest release.
• I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

The use case should be able to connect to the main queue and be always listening when a new message comes to send it to the respective consumer (e.g. email, slack).

It has to create a new record on the state machine (DB) to keep track of the notifications status.

Requirements 🌈

• Connect to the main queue (RabbitMQ Queue)
• Connect to the state machine (MongoDB)
• Connect to the consumer queue (RabbitMQ Queue)

Motivation 🔦

We need this feature in order to accomplish the MVP of the project, also, with this feature we are going to be able to make testing of the whole workflow of a event (notification).