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

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

Summary

There is no way to get notified when a batch job completes or when a company innovation score changes significantly. Webhook and notification support would enable external integrations.

What to do

  1. Add a webhooks table: url, events (list of event types), secret, enabled
  2. Expose CRUD endpoints for managing webhooks
  3. On relevant events (batch_job_complete, score_change_alert), send an HTTP POST to registered webhook URLs with an HMAC-signed payload
  4. Support at least Slack-compatible incoming webhook format as a first-class target
  5. Add a test endpoint POST /webhooks/{id}/test that sends a sample payload

Acceptance Criteria

  • Registering a webhook URL causes a POST to be sent when a batch job completes
  • The payload is HMAC-SHA256 signed; recipients can verify authenticity
  • Failed webhook deliveries are retried up to 3 times with exponential backoff
  • The frontend allows managing (create/delete/test) webhooks

Reference

Roadmap: P3 - Webhook/notification support

## Summary There is no way to get notified when a batch job completes or when a company innovation score changes significantly. Webhook and notification support would enable external integrations. ## What to do 1. Add a `webhooks` table: `url`, `events` (list of event types), `secret`, `enabled` 2. Expose CRUD endpoints for managing webhooks 3. On relevant events (`batch_job_complete`, `score_change_alert`), send an HTTP POST to registered webhook URLs with an HMAC-signed payload 4. Support at least Slack-compatible incoming webhook format as a first-class target 5. Add a test endpoint `POST /webhooks/{id}/test` that sends a sample payload ## Acceptance Criteria - Registering a webhook URL causes a POST to be sent when a batch job completes - The payload is HMAC-SHA256 signed; recipients can verify authenticity - Failed webhook deliveries are retried up to 3 times with exponential backoff - The frontend allows managing (create/delete/test) webhooks ## Reference Roadmap: P3 - Webhook/notification support
AI-Manager added the P3agent-readylarge labels 2026-03-27 18:25:42 +00:00
AI-Manager commented 2026-03-27 19:06:50 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already Implemented

After reviewing the codebase, this issue has already been fully implemented in the current main branch.

This issue can be closed.

## Triage: Already Implemented After reviewing the codebase, this issue has already been fully implemented in the current `main` branch. This issue can be closed.
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#422
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?