Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slack bot and other email alternatives #64

Open
yoavartzi opened this issue Nov 22, 2023 · 0 comments
Open

Slack bot and other email alternatives #64

yoavartzi opened this issue Nov 22, 2023 · 0 comments
Labels
planning Planning future features and development

Comments

@yoavartzi
Copy link
Member

Each user must have one push channel active. The default is email. This channel is used to send the weekly digest and potentially posting reminders (maybe combined with the digest to reduce traffic). We can consider alternatives to emails, such as a Slack bot, or other platforms that allow similar integration. This way instead of an email, the user will get a Slack message (or a sequence of messages) with the digest.

@yoavartzi yoavartzi added the planning Planning future features and development label Nov 22, 2023
@yoavartzi yoavartzi self-assigned this Nov 22, 2023
@yoavartzi yoavartzi removed their assignment Jan 2, 2024
swh00tw added a commit that referenced this issue Nov 18, 2024
## Description

<!--- Describe your changes in detail -->
Beautify slack weekly digest template

## Related Issue

<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an
issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps
to reproduce -->
<!--- Please link to the issue here: -->

- #261 
- #64 

## Notes

<!-- Other thing to say -->
Misc: I think we should add email and slack testing API endpoints back
to ease the development, but I am not sure where to add it, maybe create
`subscription.controller.ts` again? @joannechen1223

## Test

<!--- Please describe in detail how you tested your changes locally. -->

You will need to add back the `POST /subsriptions/slack/test` endpoint
to test. I will provide example code below in the comment to show how I
use mock data to test it.

## Screenshots (if appropriate):

<!--- Add screenshots of your changes here -->
The data in the screenshot were generated by `generateMock()`.

![Screenshot 2024-11-16 at 11 43
14 PM](https://github.com/user-attachments/assets/0077fe9e-03bf-462f-98e0-e1126c35d462)

## TODO

- [ ] Clear `console.log` or `console.error` for debug usage
- [ ] Update the documentation `recnet-docs` if needed
joannechen1223 added a commit that referenced this issue Nov 19, 2024
## RecNet auto-release action
This is an auto-generated PR by recnet-release-action 🤖
Please make sure to test your changes in staging before merging. 
## Related Issues
- #261
- #64
- #356
- #355
## Related PRs
- #359
- #357
- #358
## Staging links
recnet-web:
[https://vercel.live/link/recnet-git-dev-recnet-542617e7.vercel.app](https://vercel.live/link/recnet-git-dev-recnet-542617e7.vercel.app)
recnet-api:
[https://dev-api.recnet.io/api](https://dev-api.recnet.io/api)
swh00tw added a commit that referenced this issue Dec 2, 2024
## Description

<!--- Describe your changes in detail -->
Finish slack oauth flow.

## Related Issue

<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an
issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps
to reproduce -->
<!--- Please link to the issue here: -->

- #261 
- #64 

## Notes

<!-- Other thing to say -->


## Test

<!--- Please describe in detail how you tested your changes locally. -->
Before test, update `.env.local`
- `NEXT_PUBLIC_BASE_URL` should be `https://localhost:3000`
- Add `SLACK_APP_CLIENT_ID`
- Add `SLACK_OAUTH_APP_SCOPES` 
- Add`SLACK_OAUTH_REDIRECT_URI="/api/slack/oauth/callback"`

Run `nx dev:ssl recnet` and go to `https://localhost:3000`
- Go to setting and subscription tab -> Click the button to install
slack app to your workspace
- Should redirect you to slack page
- Should able to choose different workspace
- After clicking "Allow", should redirect back to frontend and see the
success message
- Go to setting again, should see the workspace name of where you
install the app


## Screenshots (if appropriate):

<!--- Add screenshots of your changes here -->
![Screenshot 2024-11-21 at 5 59
40 PM](https://github.com/user-attachments/assets/76d381f6-4dfd-49ee-976a-944b686a6d55)
![Screenshot 2024-11-21 at 5 59
50 PM](https://github.com/user-attachments/assets/092f53a1-81aa-4914-bebb-2ebc6f27f1d5)
![Screenshot 2024-11-21 at 6 00
07 PM](https://github.com/user-attachments/assets/cae362f9-58b8-4b0a-9f2a-ea4c1eb7dfc4)

## TODO

- [ ] Clear `console.log` or `console.error` for debug usage
- [ ] Update the documentation `recnet-docs` if needed
joannechen1223 added a commit that referenced this issue Dec 3, 2024
## RecNet auto-release action
This is an auto-generated PR by recnet-release-action 🤖
Please make sure to test your changes in staging before merging. 
## Related Issues
- #261
- #64
## Related PRs
- #369
- #361
- #365
- #364
- #362
## Staging links
recnet-web:
[https://vercel.live/link/recnet-git-dev-recnet-542617e7.vercel.app](https://vercel.live/link/recnet-git-dev-recnet-542617e7.vercel.app)
recnet-api:
[https://dev-api.recnet.io/api](https://dev-api.recnet.io/api)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planning Planning future features and development
Projects
Status: No status
Development

No branches or pull requests

1 participant