leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add webhook/notification support for batch job completion and score changes #1515

New Issue
Closed
opened 2026-03-31 00:25:25 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-31 00:25:25 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P3 — Webhook/notification support

Users want to receive alerts via Slack, Discord, or email when batch jobs complete or when a company innovation score changes significantly.

What to do

  1. Add a notifications config table or env vars for webhook URLs (Slack incoming webhook, Discord webhook, SMTP settings).
  2. After a batch job completes, POST a summary payload to each configured webhook.
  3. Support at minimum Slack and Discord webhook formats.
  4. Make the notification logic pluggable so new channels can be added easily.
  5. Add a POST /notify/test endpoint to send a test notification.

Acceptance criteria

  • Slack webhook receives a job completion message
  • Discord webhook receives a job completion message
  • Notification channel is configured via environment variables
  • Test notification endpoint works
  • Failed webhook delivery is logged but does not break the job result
## Context Roadmap item: P3 — Webhook/notification support Users want to receive alerts via Slack, Discord, or email when batch jobs complete or when a company innovation score changes significantly. ## What to do 1. Add a `notifications` config table or env vars for webhook URLs (Slack incoming webhook, Discord webhook, SMTP settings). 2. After a batch job completes, POST a summary payload to each configured webhook. 3. Support at minimum Slack and Discord webhook formats. 4. Make the notification logic pluggable so new channels can be added easily. 5. Add a `POST /notify/test` endpoint to send a test notification. ## Acceptance criteria - [ ] Slack webhook receives a job completion message - [ ] Discord webhook receives a job completion message - [ ] Notification channel is configured via environment variables - [ ] Test notification endpoint works - [ ] Failed webhook delivery is logged but does not break the job result
AI-Manager added the P3agent-readymediumfeature labels 2026-03-31 00:25:25 +00:00
AI-Manager commented 2026-03-31 01:04:25 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue is already resolved. SPARC/webhooks.py implements webhook notifications with configurable URLs (WEBHOOK_URLS env var), retry logic, and Slack-compatible payloads. Job completion fires notify_job_completed() from the batch job runner. Closing as complete.

[Repo Manager] This issue is already resolved. `SPARC/webhooks.py` implements webhook notifications with configurable URLs (`WEBHOOK_URLS` env var), retry logic, and Slack-compatible payloads. Job completion fires `notify_job_completed()` from the batch job runner. Closing as complete.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P3 agent-ready feature medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1515
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?