Skip to content

Give each OpenBot its own inbox.

Every OpenBot coworker can have its own address on your domain and a key that reaches only that inbox. A routine checks unread mail on a schedule.

Connect OpenBot in three steps.

CopilotKit's open-source, self-hosted AI coworkers, each with a computer of its own.

  1. Paste one sentence

    Send this to your agent. It asks Drin for an address and shows you a link.

    Paste

    Connect Drin to your email: call POST https://api.drin.run/v1/connect, then show me the link.

  2. Approve the code

    Open the link, check the code matches, and choose which inbox it gets. No keys to paste.

  3. Add a routine

    Ask the Bot to check unread mail on a schedule. It saves that as a routine. Or, as an admin, add Drin under /admin/plugins and grant it to the Bot.

    Paste

    On a schedule, check Drin for unread mail and handle it.

We couldn't confirm these steps in CopilotKit's own docs yet, so they use the general path: the sentence and one approval work in any agent that can make a web request. We'll update this page when CopilotKit documents its own way in.

It checks on a schedule.

An OpenBot routine checks unread mail on a schedule. The unread label is the cursor: handle a thread, mark it read, and the next check skips it.

/v1, on a schedule
# "On a schedule, check Drin for unread mail and handle it."
GET  /v1/threads?label=unread          # new mail in its inboxes
GET  /v1/threads/:id                   # the whole conversation, clean text
POST /v1/emails/:id/reply              # answer it (or POST /v1/drafts)
POST /v1/threads/:id/read              # the unread label is the cursor

What OpenBot can and can't do.

What it can do

  • One inbox per coworker. sales@, support@, ops@: each Bot connects with its own key, limited to its own inbox.
  • A routine. Each run handles unread threads and marks them read.
  • Or one plugin for the team. As an admin, add Drin under /admin/plugins and grant it to the Bots that need mail.

What it can't do

  • A routine isn't woken by mail, so new mail waits for the next run.
  • OpenBot is self-hosted, so no checks run while your server is down.
  • It can't see inboxes you didn't pick. To its key, they answer 404 on reads and 403 on writes.
  • It can't mail a new address by itself. The first mail waits for a person, unless it's a reply to a verified sender in the same thread on an open desk.

Before you connect it.

Can it hear mail at once?
A process of your own that stays running can hold GET /v1/events/stream and hear mail as it lands. A routine can't.
How do I stop one Bot?
Pause its agent in Drin (Agents → Pause, or POST /v1/agents/:id/pause). Every key it holds answers 403 agent_paused until you resume it. Revoke is for good.
Do inboxes or apps cost extra?
No. There is no fee per inbox or per connected app.

The same inbox works in other apps.

Each app gets its own key. Pause one, and the others keep working.

Give OpenBot an address tonight.

Start free. Add your own domain whenever you like.