Skip to content

docs(planning): ecosystem integrations and webhooks - #1300

Draft
joepio wants to merge 1 commit into
developfrom
cursor/ecosystem-integrations-webhooks-dbfa
Draft

docs(planning): ecosystem integrations and webhooks#1300
joepio wants to merge 1 commit into
developfrom
cursor/ecosystem-integrations-webhooks-dbfa

Conversation

@joepio

@joepio joepio commented Aug 20, 2026

Copy link
Copy Markdown
Member

Related Issues

Related to #976 (inbound webhooks) and #77 (outbound notifications / feeds).

What

Planning doc: planning/ecosystem-integrations.md. Maps other ecosystems against four jobs (ingress, egress, mirror, surface) and argues that a JSON Resource Event plus inbound/outbound webhooks is the first primitive — not Notion/Obsidian plugins, and not teaching n8n the binary WebSocket protocol.

Checklist

  • Add changelog entry linking to issue, describe API changes — N/A, planning only
  • Add or update tests if needed — N/A
  • Update docs if needed — planning index + cross-link from importers.md
Open in Web Open in Cursor 

Add a plan for where Atomic should meet other apps. The claim is that a
JSON Resource Event plus inbound (#976) and outbound (#77) webhooks
unblocks automation hubs, forms, chat, and CI without per-app connectors.
Notion/Obsidian stay importers and filesystem, not live sync.

Co-authored-by: joepmeindertsma <joepmeindertsma@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants