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

New Issue
Closed
opened 2026-03-26 18:24:33 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-26 18:24:33 +00:00
Owner
Copy Link
Copy Source

Context

Users have no way to be notified when long-running batch jobs complete or when a tracked company shows a significant change. Polling the API manually is cumbersome.

Work

  • Add a webhooks table to store user-configured webhook URLs and event subscriptions.
  • Trigger an HTTP POST to registered webhooks when: (a) a batch job completes, or (b) an alert fires (see scheduled analysis issue).
  • Support at minimum a generic JSON payload; optionally support Slack incoming webhook format.
  • Implement retry logic with exponential backoff for failed deliveries.
  • Expose CRUD endpoints (POST /webhooks, GET /webhooks, DELETE /webhooks/{id}) for managing webhooks.

Acceptance Criteria

  • A webhook registered for job.complete receives a POST request when a batch job finishes.
  • Failed deliveries are retried up to 3 times.
  • Webhook management endpoints are protected by JWT auth.

References

Roadmap: P3 — Webhook/notification support.

## Context Users have no way to be notified when long-running batch jobs complete or when a tracked company shows a significant change. Polling the API manually is cumbersome. ## Work - Add a `webhooks` table to store user-configured webhook URLs and event subscriptions. - Trigger an HTTP POST to registered webhooks when: (a) a batch job completes, or (b) an alert fires (see scheduled analysis issue). - Support at minimum a generic JSON payload; optionally support Slack incoming webhook format. - Implement retry logic with exponential backoff for failed deliveries. - Expose CRUD endpoints (`POST /webhooks`, `GET /webhooks`, `DELETE /webhooks/{id}`) for managing webhooks. ## Acceptance Criteria - A webhook registered for `job.complete` receives a POST request when a batch job finishes. - Failed deliveries are retried up to 3 times. - Webhook management endpoints are protected by JWT auth. ## References Roadmap: P3 — Webhook/notification support.
AI-Manager added the P3agent-readylarge labels 2026-03-26 18:24:33 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-26 19:03:12 +00:00
AI-Manager commented 2026-03-26 19:04:53 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager)

Priority: P3 | Size: Large | Agent: @senior-developer

Execution order: Wave 4 -- Partially depends on #164 for alert triggers.

Dependencies: Soft dependency on #164.

Scope: Webhooks table, HTTP POST notifications for batch completion and score changes.

## Triage (AI-Manager) **Priority:** P3 | **Size:** Large | **Agent:** @senior-developer **Execution order:** Wave 4 -- Partially depends on #164 for alert triggers. **Dependencies:** Soft dependency on #164. **Scope:** Webhooks table, HTTP POST notifications for batch completion and score changes.
AI-Manager commented 2026-03-27 01:54:56 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. SPARC/webhooks.py provides webhook/notification support. .env.example documents WEBHOOK_URLS configuration.

Closing: already implemented on main. SPARC/webhooks.py provides webhook/notification support. .env.example documents WEBHOOK_URLS configuration.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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