> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superun.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Email resume collection

> Automatically collect resume attachments from recruiting inboxes, parse candidate info, and sync to your candidate database.

# Email resume collection

Email resume collection pulls resume attachments from recruiting mailboxes, extracts candidate fields, and syncs them into your product’s candidate database. It fits ATS, talent pools, HR workspaces, and any flow that turns email attachments into structured records.

***

## What it does

* Connect a recruiting mailbox and fetch new mail on a schedule or manually.
* Detect resume emails and collect PDF attachments.
* Extract name, contact, education, experience, skills, desired role, and related fields.
* Sync candidates to your database with retry and manual upload fallbacks.

<Note>
  Underlying capabilities such as cloud, AI parsing, and file storage are provisioned by superun as needed. You usually do not configure those separately.
</Note>

***

## Before you start

| Item                      | Notes                                                                |
| ------------------------- | -------------------------------------------------------------------- |
| Recruiting mailbox        | Dedicated inbox for resumes reduces noise                            |
| Client authorization code | Use an app password or client auth code — not the web login password |
| Mail protocol             | IMAP or POP3 client access enabled                                   |
| Sample resumes            | Real or test resume emails to validate parsing                       |

***

## Mailbox requirements

No Feishu/DingTalk/WeCom permissions are required, but the mailbox provider must allow client access.

| Setting                         | Purpose              | Notes                                               |
| ------------------------------- | -------------------- | --------------------------------------------------- |
| IMAP or POP3                    | Read mail            | Usually under Settings → Client access or POP3/IMAP |
| Client auth code / app password | Sign in via protocol | Do not use the web login password                   |
| Recruiting address              | Source mailbox       | Dedicated recruiting inbox recommended              |
| Attachment format               | Parsing              | PDF preferred; keep files under \~6MB               |

Common providers:

| Provider                 | What to confirm                                |
| ------------------------ | ---------------------------------------------- |
| Tencent Enterprise Email | Client access on; client password or auth code |
| NetEase Enterprise / 163 | IMAP/POP3 on; authorization code               |
| Other enterprise mail    | IMAP/POP3 host, port, TLS, app password        |

***

## Enable in superun

<Steps>
  <Step title="Click Use">
    Open **Email resume collection** in Skill Library and click **Use** in the top-right to start integration.
  </Step>

  <Step title="Configure recruiting mailbox">
    Enter mailbox address, client auth code or app password, and confirm IMAP/POP3 is enabled.
  </Step>

  <Step title="Wire fetch and parsing">
    superun connects mail fetch, resume detection, attachment handling, and parsing to your product.
  </Step>

  <Step title="Test candidate sync">
    Send test resume mail and confirm records land in the candidate database.
  </Step>
</Steps>

***

## Limitations

* PDF resume attachments are prioritized.
* Keep PDFs under \~6MB; larger files may need manual upload or review.
* Use authorization codes or app passwords — never the mailbox login password.
* Define dedupe rules (email, phone, name + role, etc.).
* Resumes are sensitive — restrict access, log actions, and set retention/deletion policy.
* Allow recruiters to edit extracted fields; automation should not replace judgment.
* Enter mailbox secrets only in product configuration — do not paste them in public chat.
* Enabling or disabling may change project code and consume project credits.