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 #1035

New Issue
Closed
opened 2026-03-29 16:26:07 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 16:26:07 +00:00
Owner
Copy Link
Copy Source

Summary

Users have no way to be notified when a long-running batch job finishes or when a tracked company shows a significant innovation score change. Push notifications via webhooks would remove the need to poll the UI.

What to do

  • Add a notifications configuration section (Slack webhook URL, Discord webhook URL, email SMTP settings) stored in user preferences or environment variables.
  • Trigger a notification when a batch job transitions to completed or failed.
  • Trigger a notification when a scheduled analysis detects a significant change (see recurring analysis issue).
  • Use a simple outbound HTTP POST for Slack/Discord; use SMTP for email.

Acceptance criteria

  • Configuring a Slack webhook URL causes a message to be posted to Slack when a batch job completes.
  • Notification failures are logged but do not break the batch job result.
  • Notification settings are configurable without code changes.

Roadmap ref: ROADMAP.md — P3 / Webhook/notification support.

## Summary Users have no way to be notified when a long-running batch job finishes or when a tracked company shows a significant innovation score change. Push notifications via webhooks would remove the need to poll the UI. ## What to do - Add a notifications configuration section (Slack webhook URL, Discord webhook URL, email SMTP settings) stored in user preferences or environment variables. - Trigger a notification when a batch job transitions to completed or failed. - Trigger a notification when a scheduled analysis detects a significant change (see recurring analysis issue). - Use a simple outbound HTTP POST for Slack/Discord; use SMTP for email. ## Acceptance criteria - Configuring a Slack webhook URL causes a message to be posted to Slack when a batch job completes. - Notification failures are logged but do not break the batch job result. - Notification settings are configurable without code changes. Roadmap ref: ROADMAP.md — P3 / Webhook/notification support.
AI-Manager added the P3agent-readymediumfeature labels 2026-03-29 16:26:07 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 17:02:40 +00:00
AI-Manager commented 2026-03-29 17:04:23 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): Assigned to @AI-Engineer. P3 feature -- webhook/notification support for batch job completion.

**Triage (AI-Manager):** Assigned to @AI-Engineer. P3 feature -- webhook/notification support for batch job completion.
AI-Manager commented 2026-03-29 18:04:26 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. PR #66 (feature/webhooks) added webhook notification support for batch job completion and score changes. Verified: SPARC/webhooks.py exists in current main.

Resolved. PR #66 (feature/webhooks) added webhook notification support for batch job completion and score changes. Verified: SPARC/webhooks.py exists in current main.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1035
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?