Chat capture bot integration (Slack / Telegram / Discord → REST quick-capture)

[imonroe]

Summary

Provide an optional lightweight bot that lets you capture a thought into memserv by sending a chat message (Slack/Telegram/Discord), posting it to /api/v1/memories.

Idea from OB1

A core OB1 capability is "Slack/Discord capture → edge functions → vector embedding → shared database" — quick frictionless ingestion of thoughts from wherever you already are. See OB1's integrations/ (Slack/Discord capture) directory.

Why it fits memserv

• It's just another REST client of the existing bearer-auth write path — no server changes.
• Lowers the activation energy for capture, which is the main thing that makes a personal memory store actually get used.
• Fits the "single source of truth, many clients" model (PRD §1.1).

Proposed approach

• A small standalone service (could deploy as another CapRover app, like backup/) that listens to a Telegram bot / Slack slash command / Discord bot and forwards message text to POST /api/v1/memories with agent_id=capture:<platform>.
• Start with Telegram (simplest bot API, no inbound webhook infra needed via long-polling) as the reference implementation; document how to extend to Slack/Discord.
• Env-driven config (MEM0_URL, MEM0_API_KEY, bot token).

Notes / scope

OB1 routes capture through Supabase edge functions; memserv just needs a thin forwarder to the REST API. Keep it a separate optional app so the main service stays stateless.

Source: https://github.com/NateBJones-Projects/OB1