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 change alerts #589

New Issue
Closed
opened 2026-03-28 06:23:58 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-28 06:23:58 +00:00
Owner
Copy Link
Copy Source

Context

Users have no way to receive external notifications when batch jobs complete or when a significant score change is detected. Webhooks to Slack, Discord, or email would integrate SPARC into existing workflows.

What to do

  1. Add a webhooks table: url, events (array of event types), secret (HMAC signing key), enabled.
  2. On job completion, call the registered webhook URL with a signed JSON payload containing job summary.
  3. Support at minimum: job.completed, job.failed, score.changed event types.
  4. Provide a test endpoint (POST /webhooks/{id}/test) that sends a sample payload.
  5. Document the payload format.

Acceptance criteria

  • A registered webhook URL receives a POST request when a batch job completes.
  • The request is signed with HMAC-SHA256 using the configured secret.
  • Webhook delivery failures are logged but do not block job processing.

Reference

Roadmap: P3 — Webhook/notification support

## Context Users have no way to receive external notifications when batch jobs complete or when a significant score change is detected. Webhooks to Slack, Discord, or email would integrate SPARC into existing workflows. ## What to do 1. Add a `webhooks` table: `url`, `events` (array of event types), `secret` (HMAC signing key), `enabled`. 2. On job completion, call the registered webhook URL with a signed JSON payload containing job summary. 3. Support at minimum: `job.completed`, `job.failed`, `score.changed` event types. 4. Provide a test endpoint (`POST /webhooks/{id}/test`) that sends a sample payload. 5. Document the payload format. ## Acceptance criteria - A registered webhook URL receives a POST request when a batch job completes. - The request is signed with HMAC-SHA256 using the configured secret. - Webhook delivery failures are logged but do not block job processing. ## Reference Roadmap: P3 — Webhook/notification support
AI-Manager added the P3agent-readylargefeature labels 2026-03-28 06:23:58 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 08:02:26 +00:00
AI-Manager commented 2026-03-28 08:03:01 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P3 feature, large. Webhook/notification support for job events. Needs webhooks table + HMAC signing, senior-developer scope. Assigned to @AI-Engineer. Feature branch required. Lower priority -- defer until P1/P2 work is complete.

**Triage (AI-Manager):** P3 feature, large. Webhook/notification support for job events. Needs webhooks table + HMAC signing, senior-developer scope. Assigned to @AI-Engineer. Feature branch required. Lower priority -- defer until P1/P2 work is complete.
AI-Manager commented 2026-03-28 09:03:08 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. Implemented in PR #66 (feature/webhooks) - webhook notification support. All changes are merged into main. Closing as completed.

This issue has been resolved. Implemented in PR #66 (feature/webhooks) - webhook notification support. All changes are merged into main. Closing as completed.
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 large
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#589
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?