Skip to Content
ChannelsEmail

Email

Give a node a dedicated email inbox. The node reads incoming messages, drafts replies, triages spam, and can send outbound.

Status: shipping for Gmail; generic SMTP coming.

What you get

  • A dedicated email address scoped to your node. Two shapes:
    • Direktor-hosted: <node-slug>@<workspace-slug>.direktor.email — zero-setup, ready immediately.
    • Your domain (Gmail): connect a Google Workspace account and the node operates from an existing address (e.g. cmo@yourcompany.com). Uses OAuth — no password given to Direktor.
  • Inbound messages become chat messages to the node.
  • Outbound replies sent via the node’s email.
  • Attachments are staged into the workspace’s artifact shelf.
  • Full thread context preserved.

Typical use cases

  • Inbox triage — the CMO node reads cmo@yourcompany.com, labels, drafts replies, escalates anything requiring a human.
  • Form submissions — route a website contact form to a node’s address; the node drafts personalized follow-ups.
  • Newsletter ingestion — a research node subscribes to industry newsletters and summarizes weekly.
  • LinkedIn job alerts — the job-search node reads Gmail’s LinkedIn alerts and feeds them into the find-job skill.

Setup — Direktor-hosted (fastest)

  1. Workspace → Settings → Channels → Add Email → Use direktor.email address.
  2. Pick a prefix (e.g. cmo). Full address becomes cmo@acme-labs.direktor.email.
  3. Assign to a node.
  4. Send a test message — you’ll see it arrive in the node’s activity timeline within ~30 seconds.

Setup — Gmail (your domain)

  1. Workspace → Settings → Channels → Add Email → Connect Gmail.
  2. Click Sign in with Google and grant Gmail read/write scopes.
  3. Assign to a node.

Direktor uses OAuth 2.0 with refresh tokens — you never hand over your password, and you can revoke access from Google’s Security settings at any time.

Email behavior rules

  • Don’t auto-reply if the sender is a mailing list or automated notification — the node flags it for triage instead.
  • Honor reply-to headers and existing thread In-Reply-To / References to keep threads clean.
  • Don’t send bulk outbound — any skill that would send >10 emails in a session requires explicit user approval via request_approval.
  • Sensitive content — the node refuses to include credentials, security tokens, or bank details in outbound mail.

Outbound sending

Every outbound email shows the sending agent’s role in a discreet signature:

—
Sent via Direktor by the CMO agent.
Reply to this thread to continue the conversation.

You can customize the signature per node in Channels → Email → Signature.

Limitations today

  • Generic SMTP / IMAP not yet supported — Gmail only for “your domain” mode.
  • No calendar invite auto-acceptance yet (that’s a separate channel on the roadmap).
  • Large attachments (>25MB) bypass the artifact shelf and are referenced by URL only.
Last updated on
DiscordSlack