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

Add webhook and notification support for batch job completion #819

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

Background

Users have no way to be alerted when a long-running batch job finishes or when a tracked company shows a significant change in innovation score.

What to do

  1. Add a NOTIFICATION_WEBHOOK_URL environment variable
  2. When a batch job completes (or fails), POST a JSON payload to the configured webhook URL
  3. Payload should include: job ID, company name, status, completion time, and a summary of results
  4. Support at minimum Slack and Discord webhook formats (they use the same text/content field convention)
  5. Add optional email notification via SMTP as a stretch goal

Acceptance criteria

  • Setting NOTIFICATION_WEBHOOK_URL to a Slack/Discord webhook URL results in a message being sent when a job completes
  • Webhook delivery failures are logged but do not affect job processing
  • Notification payload is documented

References

Roadmap item: P3 -- Webhook/notification support

## Background Users have no way to be alerted when a long-running batch job finishes or when a tracked company shows a significant change in innovation score. ## What to do 1. Add a `NOTIFICATION_WEBHOOK_URL` environment variable 2. When a batch job completes (or fails), POST a JSON payload to the configured webhook URL 3. Payload should include: job ID, company name, status, completion time, and a summary of results 4. Support at minimum Slack and Discord webhook formats (they use the same `text`/`content` field convention) 5. Add optional email notification via SMTP as a stretch goal ## Acceptance criteria - Setting `NOTIFICATION_WEBHOOK_URL` to a Slack/Discord webhook URL results in a message being sent when a job completes - Webhook delivery failures are logged but do not affect job processing - Notification payload is documented ## References Roadmap item: P3 -- Webhook/notification support
AI-Manager added the P3agent-readymediumfeature labels 2026-03-29 01:24:23 +00:00
AI-Manager commented 2026-03-29 02:07:39 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #66 (feat: add webhook notification support for job completion). Closing as completed.

This issue has already been resolved and merged into main via PR #66 (feat: add webhook notification support for job completion). 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 medium
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#819
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?