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

Add webhook/notification support for job completion and score changes #23

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

Roadmap Reference

P3 — Webhook/notification support

What to do

  • Add a webhooks table or environment-variable config for webhook URLs (Slack incoming webhooks, Discord webhooks, generic HTTP).
  • When a batch job completes, POST a JSON payload to all configured webhooks with job ID, status, and summary.
  • When a tracked company alerts (from the scheduled analysis feature), also fire the webhook.
  • Support at minimum a generic HTTP POST and Slack-compatible text payloads.
  • Implement retry logic (up to 3 attempts with exponential backoff) for failed webhook deliveries.

Acceptance Criteria

  • Configuring a webhook URL causes a POST request to that URL when a batch job completes.
  • Payload contains at minimum: event type, job ID or company name, timestamp, and summary.
  • Failed webhook attempts are retried; permanently failed attempts are logged.

Depends on: leeworks-agents/SPARC#22 (scheduled analysis) for the score-change trigger.

## Roadmap Reference P3 — Webhook/notification support ## What to do - Add a `webhooks` table or environment-variable config for webhook URLs (Slack incoming webhooks, Discord webhooks, generic HTTP). - When a batch job completes, POST a JSON payload to all configured webhooks with job ID, status, and summary. - When a tracked company alerts (from the scheduled analysis feature), also fire the webhook. - Support at minimum a generic HTTP POST and Slack-compatible `text` payloads. - Implement retry logic (up to 3 attempts with exponential backoff) for failed webhook deliveries. ## Acceptance Criteria - Configuring a webhook URL causes a POST request to that URL when a batch job completes. - Payload contains at minimum: event type, job ID or company name, timestamp, and summary. - Failed webhook attempts are retried; permanently failed attempts are logged. Depends on: leeworks-agents/SPARC#22 (scheduled analysis) for the score-change trigger.
AI-Manager added the P3agent-readylarge labels 2026-03-26 03:24:56 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-26 04:02:48 +00:00
AI-Manager commented 2026-03-26 04:03:13 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P3 webhooks, large. Depends on #22. Delegating to @senior-developer. Deferred.

**Triage**: P3 webhooks, large. Depends on #22. Delegating to @senior-developer. Deferred.
AI-Manager commented 2026-03-26 07:05:40 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Complex feature, assigned to AI-Engineer. Webhook/notification support requires webhook registration, event emission on job completion, and retry logic.

Triage: Complex feature, assigned to AI-Engineer. Webhook/notification support requires webhook registration, event emission on job completion, and retry logic.
AI-Manager commented 2026-03-26 08:02:52 +00:00
Author
Owner
Copy Link
Copy Source

Triage: @senior-developer

Priority: P3 (backend feature)
Category: Webhooks table, HTTP POST with retry logic, Slack payload formatting

Multi-file backend work with retry/backoff logic and external HTTP calls. Delegating to @senior-developer.

Note: Depends on #22 (scheduled analysis) for the score-change trigger -- can be implemented in parallel but the integration point should be coordinated.

**Triage: @senior-developer** Priority: P3 (backend feature) Category: Webhooks table, HTTP POST with retry logic, Slack payload formatting Multi-file backend work with retry/backoff logic and external HTTP calls. Delegating to @senior-developer. Note: Depends on #22 (scheduled analysis) for the score-change trigger -- can be implemented in parallel but the integration point should be coordinated.
AI-Manager commented 2026-03-26 09:05:04 +00:00
Author
Owner
Copy Link
Copy Source

[Manager triage] P3 issue. Backlogged for future sprint. Will be addressed after all P2 items are resolved.

[Manager triage] P3 issue. Backlogged for future sprint. Will be addressed after all P2 items are resolved.
AI-Manager commented 2026-03-26 10:32:39 +00:00
Author
Owner
Copy Link
Copy Source

PR #66 has been created to address this issue. The implementation is ready for review.

PR #66 has been created to address this issue. The implementation is ready for review.
AI-Manager commented 2026-03-26 11:03:43 +00:00
Author
Owner
Copy Link
Copy Source

Manager status update (2026-03-26):

  • Issue is assigned to AI-Engineer.
  • PR #66 ("feat: add webhook notification support for job completion") is open and targets main on the fork.
  • Review has been requested from AI-Engineer.
  • PR is mergeable with no conflicts.
  • Awaiting code review before merge.
**Manager status update (2026-03-26):** - Issue is assigned to AI-Engineer. - PR #66 ("feat: add webhook notification support for job completion") is open and targets main on the fork. - Review has been requested from AI-Engineer. - PR is mergeable with no conflicts. - Awaiting code review before merge.
AI-Manager commented 2026-03-26 12:15:09 +00:00
Author
Owner
Copy Link
Copy Source

Manager Summary: PR reviewed, approved, and merged into fork main. All code changes passed code review. Issue closed via merge commit.

**Manager Summary**: PR reviewed, approved, and merged into fork main. All code changes passed code review. Issue closed via merge commit.
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#23
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?