What this does
Build a custom connector to push memories to any destination.
Requirements
- A destination that can receive HTTP requests (a webhook, an API, a queue)
- A way to host a small worker (a serverless function is fine)
- An OmegaVault account + personal access token
Setup
- Pick a destination. Anything that can ingest JSON over HTTP works: Slack, Discord, Linear, your own database, a custom internal tool.
- Write a tiny receiver. Create a single endpoint that accepts a POST with a memory payload. Shape it however makes sense for your destination.
- Register it as an outgoing webhook. In Settings → Developers → Webhooks, add an outgoing webhook pointing at your receiver. Pick the events you care about (memory.created, memory.updated).
- Test. Create a test memory in OmegaVault and watch your receiver fire. See the Webhooks reference for payload shape and retry semantics.
- Scale up. Once it's working, you can filter by collection, tag, or source — only fire the webhook when relevant memories change.
Notes & caveats
Custom connectors use the same webhook transport as any other OmegaVault automation. See the Webhooks developer docs for full details.
Official documentation
Other Connectors documentation
This guide covers the OmegaVault side. For full Other Connectors configuration, error codes, and advanced options, see the official Other Connectors documentation.
Open official Other Connectors docs ↗