Riddy21 / Riddy21/Friday_Budgeting_Pro
[Future] Notification channel configuration
Open
Nobody has claimed this yet.
enhancement
future
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Allow configuring custom notification channels (specific email, Slack webhook, etc.) instead of relying on OpenClaw's defaults.
Why later: OpenClaw already routes to whatever channel the user is on. Only needed if someone wants alerts on a different channel than their primary chat.
Rough scope:
- Channel config in DB
- Pluggable notifier (email, webhook, etc.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing OpenClaw’s current notification routing and locating the database/configuration boundary; done means a defined channel configuration and pluggable notification scope for email and webhooks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100