# Email

> Configure the Email connector with /connect so workflows can receive email events.

- Skill: `berabuddies/email` (Agent Skill)
- Install (CLI): `npx skillmds@latest add berabuddies/email`
- Raw SKILL.md: https://api.skillmd.com/api/skills/berabuddies/email/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: berabuddies (https://skillmd.com/u/berabuddies)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/berabuddies/email

---


Use `/connect email <connection>` when the user needs email workflow setup or
auth repair. That flow uses AskUserQuestion for hosts, username, app password,
from address, and allowed sender choices.

Target: $target

The `/connect` flow collects these values before configuring:

1. IMAP host, for example `imap.gmail.com`, and optional IMAP port.
2. SMTP host, for example `smtp.gmail.com`, and optional SMTP port.
3. Username, usually the full email address.
4. Password or app-specific password.
5. From address for outbound email.
6. Optional allowed sender addresses or domain suffixes such as `@example.com`.

Configuration command:

```text
/connect email <connection>
```

Treat passwords as secrets. Do not echo the password in the final answer, and
do not write it to project files. After configuration succeeds, create a
workflow with `connection_slug` set to that connection when the user wants
ongoing monitoring.