22 Replies
Awesome, so you are looking to add a docker image to the docker compose so we can test the signal provider correct?
so basically we need a base url to send request. What i understand from the signal documentation, we need to setup a docker container to get the base url.
Can you link the docs?
sure but you reffered that on the issue itself
@ut, you just advanced to level 1!
So I would recommend creating a new docker compose file in the docker folder and add the signal cli rest api container and set that up
sure got it
Once its set up then you can start building the provider to test it
one more thing
we have different options to onboard the user on signal provider like they can enter their number or scan a qr code
for first option, once the user enters their mobile number, it needs to be verified by the sms code
how to implement this thing like i checked all the sms providers. none of them verifying the number or anything
@Zac Clifton
We do not have that as the verification is typically done in the provider, however it should be easy to extend the subscriber to have this option
ok so we have to provide a new button to verify the number and when the verification is done then the provider can be added, right
@Zac Clifton
So your saying that we would need to create a new endpoint so that when we send a verification email/sms that it changes the users verified status to true in signal and in novu?
Is that correct?
something like this
probably a button when clicked sends a request to signal endpoint for verification
@ut, you just advanced to level 2!
@Zac Clifton
then the user will fill the otp that he received and the provider will be added
The only issue I see is that the subscriber would need to come onto Novu's UI to put that into our system to accept it
How do you see that process working?
the process is like subscriber will click on the signal provider to add it. after clicking he has to enter mobile number and click on generate the otp button . he then needs to put the otp in the novu ui and then click on the update button.
can you explain how you see the overall process like i think i am missing something
@Zac Clifton
I think that is perfectly doable. It will require alittle extra work on top of adding provider to be able to add that "custom action" but that will be acceptible as part of this change.
any other alternative you think i am missing or any other thing i missed
@Zac Clifton
No, I think your process is good.
The only item that is new is adding a custom button to the provider page.
ok thanks for answering questions @Zac Clifton
My pleasure
@Nikolay Knyshov This is something to consider with the design kit and redesign.
Where providers UI need to be defined dynamically in the integration store so they can run some custom process during setup.