#Unable to override "from" field for FireText provider

1 messages · Page 1 of 1 (latest)

lusty ice
#

Hi All,

We've reported an issue in the past where we could not override the "from" value when sending a FireText SMS. This was supposed to be fixed here: https://github.com/novuhq/novu/pull/4168

However, I tried today and this is still not working unfortunately (see attached picture). The "from" value being used is the one set in the FireText integration but I am expecting it to be overriden by the one from the request. Did I miss something or potential bug?

Thanks,
Boum

GitHub

What change does this PR introduce?
added support for overriding SMS

Changed worker/send-sms-usecase to support overrides
added types to node SDK
updated relevant docs

Why was this change needed?...

short thicketBOT
#

@lusty ice, you just advanced to level 2!

dapper elk
#

This merged PR will only become active in the next shipped release.

lusty ice
#

@dapper elk thanks, when would be the next release?

dapper elk
lusty ice
#

Awesome, thanks @dapper elk, I'll keep an eye on it

lusty ice
#

Hi <@&986960430528331776> - it seems that this fix was included as part of v0.20.0. However, it's still not working for me using the FireText provider. So my questions are:

  • Is overriding the "from" sender id of FireText supposed to work?
  • How can I ascertain what version of Novu is actually live? It's unclear if it's version 0.19.0 or 0.20.0

Thanks.

#

See my very first message on here for context.

#

The fix was in apps/worker/src/app/workflow/usecases/send-message/send-message-sms.usecase.ts but there's no change on that file in version 0.20.0.

Unless this was supposed to be released in the next version (i.e. 0.21.0)?

paper trail
#

@lusty ice I see above PR commits are in main branch, so it is released in 0.20.0

#

Is it not working for you?

lusty ice
#

@paper trail No, unfortunately it's not. I've tried the overrides object as seen in the screenshot of the PR which has the fix: https://github.com/novuhq/novu/pull/4168

The Sender ID being used is still the default one set in the FireText integration. I'd like to be able to override it to send SMS messages on behalf of different customers.

GitHub

What change does this PR introduce?
added support for overriding SMS

Changed worker/send-sms-usecase to support overrides
added types to node SDK
updated relevant docs

Why was this change needed?...

#

Also, there is barely any information on how the overrides object should be set to, it would be nice if the documentation was a bit descriptive:

#

And the documentation does not have version 0.20.0 in it

#

Hence when I said earlier it's unclear what version of Novu is currently live

dapper elk
teal island
lusty ice
paper trail
#

@lusty ice

Since I have non uk phone number. I have reached out to their support email for assistance to sign up and use firetext
As soon as I receive reply from them, I will quicly test this and give you an update.

paper trail
#

@lusty ice

Overrides are working with novu sms and AWS SNS provider.

lusty ice
#

Thanks @paper trail - I doubt this is an issue with FireText (we don't use SNS). Reason is if I get Novu to send an SMS using the FireText integration in which the "From" value would be set to something (see screenshot), it works as expected.

#

However, if I trigger a workflow using the FireText integration when sending an SMS but want to override the "From" value from the FireText integration like so:

#

I still get an SMS with the Sender Id that is set in the integration which should not happen looking at this line:

paper trail
#

@lusty ice Thanks for sharing
Could you please check if to and content override is working with firetext?

lusty ice
#

@paper trail No worries. I just tried the to override and it's actually working. Only the from override does not work so far. I'll try content.

short thicketBOT
#

@lusty ice, you just advanced to level 3!

lusty ice
#

@paper trail Ok so I tried again all three fields:

  • to works ✅
  • content works ✅
  • from not working ❌
paper trail
lusty ice
#

No it's not showing, instead the sender ID set in the FireText integration is used (see screenshot above). If the sender Id in the override would be invalid or filtered out, I would expect the SMS to never be received? It's still being sent but with the default From value in the FireText integration

#

That's the sender Id used when I get the SMS

#

Thanks for looking into it @paper trail, would be cool to get to the bottom of it and have a fix for it soon 🙏

paper trail
#

Sure.
We will check if provider throws (like firetext, twilio) any error with unverified from. If yes we will add this error in activity logs

zenith ledge
#

Hello everyone, I am also experiencing this issue - has there been an update on the situation?

short thicketBOT
#

@zenith ledge, you just advanced to level 1!

lusty ice
#

Hi <@&986960430528331776> - just wondered if you guys had a look at it by any chance? Thanks.

paper trail
#

<@&943775970421264404>

As from is dependent on sms provider, whether from address is authorized and verified

Few sms providers. does not throw any error on using unauthorized from
Can we handle this case?
What do you suggest?

junior onyx
#

I am not sure of any other option if they do not check it when they making a transactional message request.

junior onyx
#

Was this an accident?

paper trail
#

@safe bronze

safe bronze
lusty ice
#

Hi <@&943775970421264404> <@&986960430528331776> - I'm still encountering some challenges with the override logic and I'm quite sure that it's not related to FireText. I'd be really keen to share my findings and would appreciate the opportunity for a brief call to discuss this further. Would it be possible to arrange this? It's important for us to understand if there's a solution on the horizon, as this will help us decide our next steps. Thanks a lot for your assistance!

paper trail
#

Sent you a DM @lusty ice

paper trail
#

Hi @lusty ice

Thanks for your time
I fixed from value not picked from override issue in this PR
https://github.com/novuhq/novu/pull/4845

There were few more sms providers with firetext that were showing same issue.

I will keep you posted once it is available in our SaaS

lusty ice
#

Hi @paper trail - thank you for the very quick turnaround! It was very helpful to chat about it. Looking forward to seeing this fix go live 🚀

paper trail
#

@lusty ice
I missed updating you in this thread