Twilio Integration for client side SMS notification

[daltonfury42]

Feature: Let clients supply Twilio credentials to enable them to send SMS from their Twilio account.

Step 1:

In the queue settings, add two text boxes to enter their Account SID and Auth Token and a "Save Credentials" button.

Once the user clicks on save credentials, make a network call

PUT /me/sms
{
  "integration": "twilio"
  "accountSid": "<sid>",
  "authToken": "<token>"
}

Saving the credentials is a one time activity, on success or when the user navigates to settings again for the same or a different queue, in place of the above form, a "Clear Credentials" button should be displayed.

Clicking on the clear credentials button will make a DELETE /me/sms?integration=twilio backend call to delete the credentials.

Step 2:

If credentials are saved at backend, a "Enable SMS" toggle will be activated, which the user can use to enable and pause notifications.

This should trigger a patch call to the backend:

PATCH /queue/<queue-id>
{
  "enableSms": true/false
}

Step 3:

1. Add links and short documentation to help users create twilio credentials.
2. Add link to "Contact us if you want our team to set up SMS for for a fee".

[Burhan-Rashid]

@daltonfury42 i want to work on this feature. Pls let me know if u have any designs available for the same.

[daltonfury42]

@maaverik What is your thoughts on this one? This would allow the queue manager to set up and pay for SMS on his own, just that he will have to trust us with the credentials for twilio.

@Burhan-Rashid sorry for the late replay. You can take it up if the proposal gets accepted and if you are still interested.

[maaverik]

It's a good idea. I just feel that we should also have an explicit disclaimer saying that we are saving the credentials, but not using it for anything else and users always have the option to delete it.

[daltonfury42]

Why should we have the disclaimer? 🤔

I feel having it might make someone overly cautious and then decide not to go ahead.

[maaverik]

In my view, if someone is going to add credentials, they're already pretty technically knowledgeable, so they would expect to know that at least we've thought about securing credentials, ours being an open-source project and all.

[daltonfury42]

Okay, makes sense.

[aswath-s-tw]

@maaverik @daltonfury42 I would like to take this up. Is it taken ? And one more question, is this eligible for hacktoberfest 2022 ?

[maaverik]

Hi @aswath-s-tw, this project is not being actively maintained anymore. Thanks anyway for offering to help!