HydraDB for AgentMail

Sync AgentMail inboxes into a HydraDB knowledge graph.

AgentMail gives AI agents their own inboxes. This connector ingests that email into HydraDB as an app source, so an agent can recall past conversations before it replies.

Each message is stored as a HydraDB app_knowledge item of type email and linked to its thread node, so recall returns the whole conversation. AgentMail provides a native thread_id, so threads need no reconstruction.

Quick start

pip install hydradb-agentmail-plugin

export AGENTMAIL_API_KEY=...       # AgentMail API key
export HYDRADB_API_KEY=...         # HydraDB API key
export HYDRADB_DATABASE=...        # target database (tenant)

agentmail-sync             # every inbox
agentmail-sync <inbox_id>  # one inbox

Behavior

• With no argument, lists all inboxes and syncs each. Pass an inbox id to scope to one.
• Uses AgentMail's reply-stripped extracted_text, falling back to text then preview. Caps body length at 8000 characters.
• Links each message to an agentmail-thread-<thread_id> node and to its parent via in_reply_to, so threads and reply chains come back connected.
• Set AGENTMAIL_AFTER (ISO 8601) to pull only messages after a cutoff.
• Query with query_apps: true (the default) to search this email alongside other app sources.

Configuration

Field mapping

AgentMail's message_id is the RFC Message-ID, so in_reply_to already equals the parent's node id once angle brackets are stripped. The parent upserts to the same id on its own sync, so reply edges connect across incremental runs.

Live ingest

Run on a schedule for a backfill, or call it from an AgentMail message.received / message.sent webhook to ingest each email on arrival. message_to_item and ingest_items are importable for the webhook path.

License

MIT. See LICENSE.