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

New Issue
Closed
opened 2026-03-26 14:24:16 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-26 14:24:16 +00:00
Owner
Copy Link
Copy Source

Context

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

  • Design a webhooks or notifications table to store user-configured notification endpoints and event types.
  • Implement a notification dispatch service that sends HTTP POST payloads to configured URLs on job.completed and score.changed events.
  • Add at minimum Slack and generic webhook targets (Discord is compatible with Slack payloads).
  • Provide a UI settings page for users to configure their webhook URL and select events.
  • Document the webhook payload schema.

Acceptance Criteria

  • Configuring a webhook URL and completing a batch job triggers a POST to that URL.
  • The payload includes job ID, status, company name, and timestamp.
  • Failed webhook deliveries are logged.

References

Roadmap: P3 — webhook/notification support.

## Context 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 - Design a `webhooks` or `notifications` table to store user-configured notification endpoints and event types. - Implement a notification dispatch service that sends HTTP POST payloads to configured URLs on `job.completed` and `score.changed` events. - Add at minimum Slack and generic webhook targets (Discord is compatible with Slack payloads). - Provide a UI settings page for users to configure their webhook URL and select events. - Document the webhook payload schema. ## Acceptance Criteria - Configuring a webhook URL and completing a batch job triggers a POST to that URL. - The payload includes job ID, status, company name, and timestamp. - Failed webhook deliveries are logged. ## References Roadmap: P3 — webhook/notification support.
AI-Manager added the P3agent-readylarge labels 2026-03-26 14:24:16 +00:00
AI-Manager commented 2026-03-26 15:06:29 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. Webhook/notification support for batch job completion and score changes implemented. Implemented in PR #66 (merged). See SPARC/webhooks.py.

Resolved. Webhook/notification support for batch job completion and score changes implemented. Implemented in PR #66 (merged). See `SPARC/webhooks.py`.
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#88
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?