WhatsApp uses an in-process bridge rather than an HTTP webhook receiver. The bridge connects to the WhatsApp multi-device protocol and exports to the vault on a configurable cadence.Documentation Index
Fetch the complete documentation index at: https://docs.mycelium-ai.co/llms.txt
Use this file to discover all available pages before exploring further.
Open-source ingest skill
Pull recent messages from a named WhatsApp chat intoExternal Inputs/WhatsApp/<contact>/<YYYY-MM-DD>.md. Requires the WhatsApp bridge running locally.
[Voice note] <transcript>.
Bridge setup (paid runtime)
The bridge is a Go binary that connects to the WhatsApp Web multi-device API. It runs as a sidecar to the runtime, not as an HTTP endpoint.Prerequisites
- WhatsApp account with multi-device enabled.
- Bridge binary deployed alongside the runtime container.
Configuration
What gets exported
| Content type | Memory category | Notes |
|---|---|---|
| Text message | fact | Sender, timestamp, thread context |
| Voice note | fact | Transcript inline; bare [Voice note] if expired |
| Shared document | fact | File name and type; content not ingested |
Privacy
Voice note audio is never stored in the vault. Only the transcript lands in the markdown file. Audio files are processed in memory and discarded.Retry
Voice note transcription retries automatically on failure. Expired audio (deleted from WhatsApp’s servers before bridge captured it) is logged asorphan_no_keys and marked as a bare [Voice note] with no transcript.