leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Feature: webhook and notification support for completed batch jobs and score changes #894

New Issue
Closed
opened 2026-03-29 05:24:23 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 05:24:23 +00:00
Owner
Copy Link
Copy Source

Context

Users have no way to be notified when long-running batch jobs complete or when a company score changes significantly without polling the dashboard.

Roadmap reference: P3 - Webhook/notification support

What to do

  1. Add a webhooks configuration table (URL, event types: job_complete, score_change).
  2. After a batch job completes or a score threshold is crossed, POST a JSON payload to configured webhook URLs.
  3. Support at least Slack-compatible payloads (simple JSON with text field).
  4. Expose webhook CRUD via the API.
  5. Optionally: support email via SMTP with configurable credentials.

Acceptance criteria

  • A configured webhook URL receives a POST request when a batch job completes.
  • The payload includes job ID, company name, completion time, and a summary.
  • Failed webhook deliveries are logged (not silently dropped).
## Context Users have no way to be notified when long-running batch jobs complete or when a company score changes significantly without polling the dashboard. Roadmap reference: P3 - Webhook/notification support ## What to do 1. Add a `webhooks` configuration table (URL, event types: `job_complete`, `score_change`). 2. After a batch job completes or a score threshold is crossed, POST a JSON payload to configured webhook URLs. 3. Support at least Slack-compatible payloads (simple JSON with `text` field). 4. Expose webhook CRUD via the API. 5. Optionally: support email via SMTP with configurable credentials. ## Acceptance criteria - A configured webhook URL receives a POST request when a batch job completes. - The payload includes job ID, company name, completion time, and a summary. - Failed webhook deliveries are logged (not silently dropped).
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 05:24:23 +00:00
AI-Manager commented 2026-03-29 06:03:01 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The changes are already merged into main.

Webhook notification support added via webhooks.py for job completion and score changes.

Closing as completed.

This issue has been resolved. The changes are already merged into main. Webhook notification support added via webhooks.py for job completion and score changes. 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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