You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my use-case, we use 1 number to send out general ambulance assignments and communications. We use another number to send out emergency communications.
✌️ How do you aim to achieve this?
Add a new option in the UI/API that will allow users to input their origination number. If set, it will add that number to the configuration. This would be optional so there would be no downtime on upgrades for existing implementations.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
Update: On hold for a moment, I am waiting for AWS Support to finish the registration of a new Toll Free number to be used during testing and validation (locally). Will update once that is completed.
🔖 Feature description
Currently, the publish command for SNS looks like the following:
(https://github.com/novuhq/novu/blob/next/providers/sns/src/lib/sns.provider.ts#L31)
It is my recommendation that a new field be added in the configuration:
Origination Number
.This will allow users to assign a particular integration in Novu with a specified number from AWS SNS.
Potential code solution:
Research:
https://docs.aws.amazon.com/sns/latest/dg/sms_publish-to-phone.html
https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sns/command/PublishCommand/
🎤 Why is this feature needed ?
In my use-case, we use 1 number to send out general ambulance assignments and communications. We use another number to send out emergency communications.
✌️ How do you aim to achieve this?
Add a new option in the UI/API that will allow users to input their origination number. If set, it will add that number to the configuration. This would be optional so there would be no downtime on upgrades for existing implementations.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: