Built-in email manager for the Afina antidetect browser

Connect IMAP mailboxes once, attach them to profiles, read codes and confirmations inside RPA scripts. Account verification stops being the bottleneck — Afina watches the inbox so you don't have to.

IMAP • Per-account • Encrypted

Email confirmations, without leaving the browser

Every multi-account workflow eventually hits an email confirmation step. Most teams glue a Python script + Gmail API on the side. Afina ships the IMAP layer natively: credentials encrypted per account, inbox monitoring built into the desktop, and read access exposed inside RPA flows and the local API.

IMAP credentials, encrypted

Add email/password/IMAP server/port once and Afina stores credentials encrypted at rest (passwords never come back via the API, only metadata). Activate or deactivate mailboxes without re-entering keys.

Mailbox per profile

Attach an inbox to one or many profiles. The same email can serve multiple accounts (alias plus tags), or a unique inbox per profile if your platform demands it.

Read emails inside RPA scripts

A built-in "wait for email" block matches subject/from/regex, returns the body to the flow, and forwards verification codes straight into form fields — no executeModule glue needed. Stack with modules for richer parsing.

Local-first, leak-aware

IMAP connections respect the per-profile proxy and DNS settings. No external mail-API webhooks, no shared inbox — emails enter and exit your machine like everything else in Afina.

FAQs

Have questions? We're here to help.

Online Support Available

Telegram Discord

Anything that speaks IMAP — Gmail (with app passwords or OAuth), Outlook/Hotmail, Yahoo, Yandex, ProtonMail Bridge, custom corporate IMAP. Specify server, port, SSL settings; Afina handles the connection.

Passwords are encrypted at rest with your master key and never returned through any API endpoint. Read access in scripts works through internal handles, not by exposing the password. Disable mailboxes from the UI to instantly close all open IMAP connections.

Drop the wait-for-email block — set the inbox, match conditions (subject contains, from regex, body keyword, time-window) and a timeout. The block returns the matching message body so you can extract codes, links or arbitrary content for the next step.

Yes. Toggle isActive on a mailbox via UI or POST /api/emails/toggle — Afina opens a persistent IMAP connection and surfaces new messages via internal events. The wait-for-email block in scripts subscribes to that stream rather than polling.

Yes — Gmail-style + aliases work fine. Attach the inbox to several profiles and route messages by match conditions (e.g. subject 'Confirm account for {{accountId}}'). For platforms that require unique mailboxes, use per-profile credentials.

Yes. The connection goes through the per-profile proxy (HTTP CONNECT for HTTP proxies, native SOCKS5 for SOCKS). DNS resolution follows the same path, so the mail server sees the proxy IP just like the browser does.

Stop juggling Gmail tabs — wire IMAP in once

Add credentials, attach to profiles, drop the wait-for-email block into your flow. Verification just works.

The Afina email manager attaches an IMAP mailbox to every browser profile: per-account credentials, encrypted at rest in the zero-knowledge vault, and readable directly from RPA scripts and Node.js modules. Confirmation codes, password resets, 2FA emails — all available inline in your automation without exporting to third-party services.

Sharing one mailbox across accounts is the easiest way to get a portfolio linked — anti-fraud cross-checks recovery emails and 2FA destinations. Per-account email also unlocks fully automated account creation: spin up a profile, read the confirmation code from its mailbox, submit, done. No copy-paste, no manual baby-sitting.

What's inside the email manager

1. IMAP credentials per account

Each profile carries its own IMAP server, port, login, password and folder mapping. Supports any provider that speaks IMAP — Gmail, Outlook, Yandex, custom domains, anti-fraud-safe disposable providers.

2. Encrypted credential storage

Passwords sealed with your local zero-knowledge key. Storage only sees sealedBox blobs. Even a stolen profile dump or a compromised sync target reveals nothing in cleartext.

3. Read mail inline in RPA

RPA blocks: read latest unread, search by subject regex, extract from body, extract from link. The script pauses for the mail to arrive, parses the code, continues — without a human in the loop.

4. Use in Node.js modules

The same IMAP credentials are available inside signed modules for custom logic — multi-message parsing, attachment download, header inspection, anti-spam learning, anything Node IMAP libs support.

5. Bulk import and rotation

Upload an Excel of IMAP credentials, map to profile groups, rotate when needed. The same primitives that drive multi-accounting at scale — applied to mailboxes.

Where the email manager makes flows work

Account creation flows on platforms that require email confirmation. Password rotation runs that read reset links from the mailbox. Airdrop farming with per-wallet emails to dodge Sybil clusters. Affiliate portfolios where each ad account needs its own recovery address. Auto-onboarding on SaaS trials. Without per-account email built into the antidetect stack, every one of these turns into manual work.