Mark/mesh-seed

Fork 0

[Priority 2] N8N integration - webhook to Redis bridge #4

New issue

Closed

opened 2026-03-10 20:45:14 +00:00 by Mark · 2 comments

Mark commented

2026-03-10 20:45:14 +00:00

Owner

Connect N8N automation platform to mesh backplane.

Implementation

N8N workflow: Webhook receiver → Redis publish
Triggers on: /mesh/intent endpoint
Publishes to: mesh.intent.discovered channel

Use cases

External systems submit intents via HTTP
Scheduled tasks (cron) emit intents
Forgejo webhooks trigger mesh workflows

See

IMMEDIATE_INTEGRATION.md (Action 1)

Connect N8N automation platform to mesh backplane. ## Implementation - N8N workflow: Webhook receiver → Redis publish - Triggers on: /mesh/intent endpoint - Publishes to: mesh.intent.discovered channel ## Use cases - External systems submit intents via HTTP - Scheduled tasks (cron) emit intents - Forgejo webhooks trigger mesh workflows ## See - IMMEDIATE_INTEGRATION.md (Action 1)

Mark referenced this issue

2026-03-14 18:59:23 +00:00

[Phase 2] Federation - Multi-Node Mesh #29

Mark commented

2026-03-14 19:00:04 +00:00

Author

Owner

Phase Tracking: This issue is part of Phase 2: Federation

Status: 🔴 NOT STARTED

Dependencies:

Depends on: Phase 0 completion
Related: #6 (Forgejo webhooks), #7 (Service discovery)

Acceptance Criteria:

N8N workflow receives HTTP webhooks
Publishes to Redis intent.discovered channel
Documented in USAGE.md

**Phase Tracking:** This issue is part of [Phase 2: Federation](https://forgejo.tail018ac4.ts.net/Mark/mesh-seed/issues/29) **Status:** 🔴 NOT STARTED **Dependencies:** - Depends on: Phase 0 completion - Related: #6 (Forgejo webhooks), #7 (Service discovery) **Acceptance Criteria:** - N8N workflow receives HTTP webhooks - Publishes to Redis `intent.discovered` channel - Documented in USAGE.md

Mark referenced this issue

2026-03-14 19:00:10 +00:00

[Priority 2] Forgejo webhooks → mesh intents #6

Mark commented

2026-03-15 01:07:07 +00:00

Author

Owner

✅ IMPLEMENTED - N8N Integration Complete

Status: Complete and tested

Implementation:

runtime/n8n_bridge.py - Flask webhook receiver
Accepts POST requests at /mesh/intent
Validates incoming N8N payloads
Transforms to mesh intent format
Publishes to Redis mesh.intent.discovered
Returns intent_id to N8N

Configuration:

Port: 5001 (configurable)
Auth token validation
Redis integration

Documentation: docs/N8N_INTEGRATION.md

Tests: tests/integration/test_n8n_bridge.py

Closing as implemented in Phase 2 Federation work.

## ✅ IMPLEMENTED - N8N Integration Complete **Status:** Complete and tested **Implementation:** - `runtime/n8n_bridge.py` - Flask webhook receiver - Accepts POST requests at `/mesh/intent` - Validates incoming N8N payloads - Transforms to mesh intent format - Publishes to Redis `mesh.intent.discovered` - Returns intent_id to N8N **Configuration:** - Port: 5001 (configurable) - Auth token validation - Redis integration **Documentation:** `docs/N8N_INTEGRATION.md` **Tests:** `tests/integration/test_n8n_bridge.py` Closing as implemented in Phase 2 Federation work.

Mark closed this issue

2026-03-15 01:07:25 +00:00

~~Mark referenced this issue 2026-03-15 01:08:12 +00:00~~

[Meta] Project Status - March 2026 #32

Mark referenced this issue

2026-08-04 23:35:46 +00:00

skill_executor.py passes 'capability_id' to MeshLedger but refactored API expects 'contract_id' — 3 test failures, 6 call sites #253

Mark referenced this issue from a commit

2026-08-12 11:44:47 +00:00

test(#271): assert 6000-char budget via public EmbedBuilder path