Inboxes
An inbox is a connected mailbox ForgeSend can send campaign emails from and check for replies on. Every inbox belongs to exactly one workspace and shows up as a sender option across Campaigns — the sender pool is built from whichever inboxes are CONNECTED in the active workspace. Inboxes is its own sidebar item, built from three pieces: a connect panel, a card grid, and a detail slide-over.
On this page
The Inboxes page
On desktop, the connect panel is a persistent left column, always visible next to the card grid — there's no separate "add inbox" button to hunt for. On narrower screens it collapses to a slim Add sending identity trigger that expands the same panel over the grid.
Add sending identity
Connect a new mailbox to this workspace.
Google Workspace
Connect Gmail or Google Workspace with OAuth.
Microsoft 365 / Outlook
Connect Outlook or Microsoft 365 with OAuth.
SMTP / Manual
Connect using SMTP credentials and optional IMAP reply sync.
With nothing connected yet, the grid shows a single centered card instead: "No inboxes connected" — "This is the account your campaigns actually send from. Connect a Google Workspace, Microsoft 365, or self-hosted SMTP mailbox — OAuth takes under a minute, and credentials are encrypted at rest either way."
This replaces the previous single-column list entirely, at any inbox count — there's no fallback to a list view. Every inbox is a card in a responsive grid (one column on mobile, two from sm, three from lg), and every card is clickable: clicking one is the only way to open its detail slide-over, covered below.
Providers
ForgeSend connects three kinds of sending identity:
- Google — Gmail or Google Workspace, via OAuth
- Microsoft — Outlook or Microsoft 365, via OAuth
- SMTP_IMAP — any other provider (Zoho, cPanel-hosted mail, AWS SES, etc.), via manual SMTP credentials with optional IMAP for reply fetching
Each inbox is uniquely identified by its workspace, provider, and email address — connecting the same mailbox again updates the existing inbox rather than creating a duplicate. Full setup detail for each — including the exact OAuth scopes and SMTP presets — is in Connecting an inbox.
The card grid
Every card is a pure at-a-glance summary — there are deliberately no inline action buttons on a card. Every action (daily limit, signature, reconnect, disconnect, domain checks) lives one click away, in the slide-over.
A card shows, top to bottom: the email address and a provider chip (GOOGLE / M365 / SMTP); a status pill plus either a health chip ({score} · {label}) or, if the inbox is Disconnected, an Unavailable pill in place of health; a thin daily-send usage bar with {sentToday}/{dailyLimit} sent today; and, if the inbox has ever run warmup, a lifecycle badge that links straight to its warmup detail page without opening the slide-over.
The detail slide-over
Clicking anywhere on a card slides a 480px panel in from the right, titled with the inbox's email address. Its sections, in order:
Domain authentication
Placement & reputation
Landed in the inbox — last 30 days
91%
View full history and detail →
Sending
Signature
Edit signature
- Domain authentication — live SPF/DKIM/DMARC checks for the inbox's own domain. A missing record shows an amber "Not yet verified", not a red error — it's presented as something to go add, not a fault. If more than one connected inbox shares a domain, a note clarifies the result applies to the whole domain, not just this inbox.
- Placement & reputation — a single rolled-up stat, not the full chart: the percentage of the inbox's sends that landed in the inbox (rather than spam) over the last 30 days, or "Not enough data yet". View full history and detail links out to that inbox's tab on the Warmup page for the complete trend.
- Sending — the daily-limit editor, covered in Signatures and daily limits.
- Signature — opens the signature modal, also covered in Signatures and daily limits.
- Connection settings and Token — OAuth-only; omitted entirely for SMTP inboxes, since there's no token to refresh.
- Disconnect (or Reconnect, once disconnected or errored) — covered in Connecting an inbox.
Connection status
Every inbox has one of three statuses:
- Connected — eligible to send and, for OAuth inboxes, has auto-refreshing tokens
- Disconnected — either manually disconnected, or an OAuth token failed and needs reconnecting; excluded from sending until reconnected
- Error — the same exclusion as Disconnected, but reached from a connection failure rather than a manual action
Disconnecting an inbox does not delete it — see Connecting an inbox for exactly what's preserved.
Where to go next
Next: Connecting an inbox — Google, Microsoft, and SMTP/IMAP setup
- Signatures and daily limits
- Inbox health and rotation
- Deliverability overview — the separate workspace-level readiness view
- Campaigns overview — sender pool and sending behavior