Publishing on SQS through Novu
Hey guys, a client asks us to push their notifications on an AWS SQS queue.
We'd like to use Novu for that for multiple reasons (notification unicity, reuse of all our existing notification templates, etc...).
What would be required for this integration to be possible ?
Thank you !
14 Replies
Hey @Norrude do you want to use SQS for the queue?
My question revolves more around having SQS as one of the Novu providers, to be able to publish on SQS as if it was a Novu Notification
Or I should probably look into: https://docs.aws.amazon.com/sns/latest/dg/subscribe-sqs-queue-to-sns-topic.html
Subscribing an Amazon SQS queue to an Amazon SNS topic - Amazon Sim...
To enable an Amazon SNS topic to send messages to an Amazon SQS queue, do one of the following:
So if you are looking to use AWS as a provider you can use (SNS for push notifications web and mobile, or SES for emaik), SQS would be an underlying queue for comminuting with Novu, or queue system for Novu. Based on what you are referring to I think SNS or SES might be what you are looking for.
As I said, our clients want their notifications on SQS.
So as long as I don't have published messages on SQS, then I don't have what I need...
Here is our usecase:
We send notifications to clients:
- Email (SES)
- Messages (SNS)
- Chat (Slack webhooks, ...)
- Enqueued notifications on SQS for in app integrations by our customers (???)
Thanks for that @Norrude, let me get @Dima Grossman here, I think he might be able to help us.
It seems my previous message about using SNS subscriptions as a way to publish on SQS is not possible, as Novu doesn't publish on SNS topics, but directly to SNS text messaging (SMS)
@Norrude this is true.
Have you seen https://docs.novu.co/echo/quickstart by chance? You can use a
custom step type there to trigger an SQS push there.Novu
Quick Start - Novu
Novu Echo, the Code-first notification workflow engine. Build advanced workflows while giving your non-technical teammates complete control over content and behaviour.
Hey @Dima Grossman,
Thanks, I didn't see it, this sounds promising.
We currently aren't using Echo, is there an easy way for me to use it exclusively for that usecase and keep the rest to be managed in app ?
@Norrude, you just advanced to level 2!
@Norrude you can have regular workflows + Echo workflows living side by side
Is there a way to even add those steps to pre-existing workflows, not built with Echo ?
Like workflow_1 having a chat, and email notification on the app, and adding the custom step from echo using its workflowId from the Novu app ?
Or does it need to be two different workflows ?
How likely it is that Echo will have breaking changes ?
@Dima Grossman ?
@Norrude currently workflows defined in Echo are entirely defined there. So you can't have half workflow with UI and half with Echo. This is something we might be looking forward to add support for in the future but currently.
Regarding breaking changes, the API is mostly finalized and any further changes will be versioned with migration paths in case of breaking changes. You can stick with a specific version for now