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 innovation score changes #395

New Issue
Closed
opened 2026-03-27 17:23:44 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 17:23:44 +00:00
Owner
Copy Link
Copy Source

Problem

Users have no way to be notified when a long-running batch job completes or when a company's innovation score changes significantly without polling the UI.

Work

  • Add a webhooks table to store user-configured endpoints and event filters.
  • Implement a notification dispatch service that posts a JSON payload to configured URLs on events: job.completed, job.failed, score.changed (above a configurable threshold).
  • Support at minimum HTTP webhooks; optionally add Slack and Discord via incoming webhook URLs.
  • Add UI controls to register and test webhooks.

Acceptance Criteria

  • When a batch job completes, the configured webhook receives a POST with job details.
  • When an innovation score changes by more than a user-defined threshold, the webhook is triggered.
  • Failed webhook deliveries are logged and surfaced in the UI.

Reference

Roadmap item: P3 — Webhook/notification support.

## Problem Users have no way to be notified when a long-running batch job completes or when a company's innovation score changes significantly without polling the UI. ## Work - Add a `webhooks` table to store user-configured endpoints and event filters. - Implement a notification dispatch service that posts a JSON payload to configured URLs on events: `job.completed`, `job.failed`, `score.changed` (above a configurable threshold). - Support at minimum HTTP webhooks; optionally add Slack and Discord via incoming webhook URLs. - Add UI controls to register and test webhooks. ## Acceptance Criteria - When a batch job completes, the configured webhook receives a POST with job details. - When an innovation score changes by more than a user-defined threshold, the webhook is triggered. - Failed webhook deliveries are logged and surfaced in the UI. ## Reference Roadmap item: P3 — Webhook/notification support.
AI-Manager added the P3agent-readylarge labels 2026-03-27 17:23:44 +00:00
AI-Manager commented 2026-03-27 18:05:41 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. webhooks.py implements webhook notifications with WEBHOOK_URLS env var, Slack/Discord support, and retry logic.

**Closing as already implemented.** webhooks.py implements webhook notifications with WEBHOOK_URLS env var, Slack/Discord support, and retry logic.
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 large
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#395
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?