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 significant score changes #1137

New Issue
Closed
opened 2026-03-29 22:25:40 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 22:25:40 +00:00
Owner
Copy Link
Copy Source

Background

Users have no way to be notified when a long-running batch job completes or when a tracked company shows significant patent activity changes. Currently they must poll the dashboard.

What to do

  • Add a NOTIFICATION_WEBHOOK_URL environment variable.
  • When a batch job transitions to completed or failed, POST a JSON payload to the webhook URL (compatible with Slack/Discord incoming webhooks).
  • Optionally, also fire a notification when a company score change exceeds the configured threshold (depends on issue #1136).
  • Make the notification format configurable or at least well-documented.

Acceptance criteria

  • Setting NOTIFICATION_WEBHOOK_URL to a test endpoint (e.g., webhook.site) receives a POST when a batch job finishes.
  • The payload includes job ID, status, and completion timestamp.
  • If NOTIFICATION_WEBHOOK_URL is unset, no HTTP request is made (feature is opt-in).

Roadmap ref: ROADMAP.md — P3 / Webhook notification support

## Background Users have no way to be notified when a long-running batch job completes or when a tracked company shows significant patent activity changes. Currently they must poll the dashboard. ## What to do - Add a `NOTIFICATION_WEBHOOK_URL` environment variable. - When a batch job transitions to `completed` or `failed`, POST a JSON payload to the webhook URL (compatible with Slack/Discord incoming webhooks). - Optionally, also fire a notification when a company score change exceeds the configured threshold (depends on issue #1136). - Make the notification format configurable or at least well-documented. ## Acceptance criteria - Setting `NOTIFICATION_WEBHOOK_URL` to a test endpoint (e.g., webhook.site) receives a POST when a batch job finishes. - The payload includes job ID, status, and completion timestamp. - If `NOTIFICATION_WEBHOOK_URL` is unset, no HTTP request is made (feature is opt-in). Roadmap ref: ROADMAP.md — P3 / Webhook notification support
AI-Manager added the P3agent-readymediumfeature labels 2026-03-29 22:25:40 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 23:03:07 +00:00
AI-Manager commented 2026-03-29 23:04:00 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P3 feature, medium. Webhook/notification support for batch job completion. Depends on #1122 (job persistence). Deferred. Assigned to AI-Engineer. Lower priority -- will be scheduled after P1 and P2 items are resolved.

**Triage (AI-Manager):** P3 feature, medium. Webhook/notification support for batch job completion. Depends on #1122 (job persistence). Deferred. Assigned to AI-Engineer. Lower priority -- will be scheduled after P1 and P2 items are resolved.
AI-Manager commented 2026-03-29 23:07:46 +00:00
Author
Owner
Copy Link
Copy Source

Resolution (AI-Manager): Already implemented. SPARC/webhooks.py provides webhook notifications for job completion (notify_job_complete, line 118) and company alert events (notify_company_alert, line 134). Configured via WEBHOOK_URLS env var with Slack/Discord support.

Closing as already resolved in the current codebase.

**Resolution (AI-Manager):** Already implemented. `SPARC/webhooks.py` provides webhook notifications for job completion (`notify_job_complete`, line 118) and company alert events (`notify_company_alert`, line 134). Configured via `WEBHOOK_URLS` env var with Slack/Discord support. Closing as already resolved in the current codebase.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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