wdevs/amcs
5
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Add webhook ingestion endpoint for external sources #8

New Issue
Closed
opened 2026-04-03 11:12:38 +00:00 by sam · 3 comments
sam commented 2026-04-03 11:12:38 +00:00
Member
Copy Link
Copy Source

Summary

Add a generic webhook ingestion path so external systems can push events, notes, or content into AMCS without going through the MCP interface directly.

Why

Webhook ingestion is explicitly listed as deferred in the implementation plan and would make AMCS easier to integrate with automation tools and external services.

Scope ideas

  • Define one or more authenticated webhook endpoints
  • Establish a stable payload schema for thought content, metadata, project, and source
  • Support source-specific metadata passthrough where safe
  • Validate and normalize inbound payloads before persistence
  • Add rate limiting / idempotency handling where appropriate
  • Document example integrations

Acceptance criteria

  • A documented webhook flow exists for creating AMCS thoughts from external systems
  • Authentication and validation rules are explicit
  • Payload normalization produces consistent thought records
  • README/config docs include setup examples

Source

Deferred feature from llm/plan.md: webhook ingestion.

## Summary Add a generic webhook ingestion path so external systems can push events, notes, or content into AMCS without going through the MCP interface directly. ## Why Webhook ingestion is explicitly listed as deferred in the implementation plan and would make AMCS easier to integrate with automation tools and external services. ## Scope ideas - Define one or more authenticated webhook endpoints - Establish a stable payload schema for thought content, metadata, project, and source - Support source-specific metadata passthrough where safe - Validate and normalize inbound payloads before persistence - Add rate limiting / idempotency handling where appropriate - Document example integrations ## Acceptance criteria - A documented webhook flow exists for creating AMCS thoughts from external systems - Authentication and validation rules are explicit - Payload normalization produces consistent thought records - README/config docs include setup examples ## Source Deferred feature from `llm/plan.md`: webhook ingestion.
sgcommand commented 2026-07-15 03:03:46 +00:00
Member
Copy Link
Copy Source

Implemented in PR #39

Branch: issue-8-webhook-ingestion
Commit: fe82678280
Verification: make test; make build

Summary: Adds authenticated POST /webhooks/thoughts for external JSON ingestion, thought metadata normalization, sanitized webhook source metadata, and idempotency-key duplicate handling.

Implemented in PR #39 Branch: issue-8-webhook-ingestion Commit: fe8267828043f030795da2d9164e933b7189c299 Verification: make test; make build Summary: Adds authenticated POST /webhooks/thoughts for external JSON ingestion, thought metadata normalization, sanitized webhook source metadata, and idempotency-key duplicate handling.
sgcommand commented 2026-07-15 03:05:49 +00:00
Member
Copy Link
Copy Source

Update for PR #39

Branch: issue-8-webhook-ingestion
Commit: e459775740
Verification: make test; make build

Note: CI workflow was also updated to build the embedded UI before go test/go build so clean runners have internal/app/ui/dist available.

Update for PR #39 Branch: issue-8-webhook-ingestion Commit: e459775740993452ea2175b0f3ec719c27ebc13b Verification: make test; make build Note: CI workflow was also updated to build the embedded UI before go test/go build so clean runners have internal/app/ui/dist available.
sgcommand commented 2026-07-15 10:51:21 +00:00
Member
Copy Link
Copy Source

Closing after verification: PR #39 (#39) was merged on 2026-07-15T04:35:20Z and implements this issue. Verification recorded in the PR/issue comments: make test; make build.

Closing after verification: PR #39 (https://git.warky.dev/wdevs/amcs/pulls/39) was merged on 2026-07-15T04:35:20Z and implements this issue. Verification recorded in the PR/issue comments: make test; make build.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
debugging
integration
planned
ux
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hein (Hein) root sam sgcommand (SG Command) warkanum (Warky)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/amcs#8
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?