Skip to main content
Upload a CSV of mailboxes you already run, and each row becomes an email account in this workspace, verified the same way as one you connect by hand.
Where
Integrations→Integrations→Email Accounts
Your role needs
Read access to Email Accounts read-senders. Admin, Member and Viewer have it by default.
To create or change
create-senders to add one, update-senders to change one, on top of the permission above.
If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.

​
Before you begin

  • Every account you import lands in the workspace you’re currently in. Switch workspaces first if you keep more than one.
  • Ten fields are required: the address, a first name, and the IMAP and SMTP host, username, password and port. Your file needs fewer columns than that. Both usernames are filled from the address column, and one password column is copied across to the other protocol, so address, first name, both hosts, both ports and a single password resolve all ten. Last name, a signature and a tracking domain are optional. Connecting a mailbox by hand asks for the same technical details, if you need to look any of them up first.
  • A row whose address is already an email account in this workspace updates that account rather than adding a second one: the file’s server settings, password and name replace what is stored, this batch’s limit and delay replace the account’s own, and this batch’s sending windows are added to the ones it already has.
  • An address that belongs to an email account in a different workspace cannot be imported. That row fails and nothing is created for it.

​
Steps

1

Open the import wizard

From Email Accounts (), open Add senders and choose the Import senders card: its button reads Import CSV. With no email accounts at all, the empty page puts the same route one click closer: an Import Senders button sits right next to Add senders.The same panel also connects a single mailbox you own, and, in workspaces that offer it, orders infrastructure we set up for you. Both are covered on the Add senders page, linked below.
2

Upload your CSV

Drop a file onto the panel, or use Browse files to pick one. The file has to be a .csv, and one with no rows under its header is rejected too. Download template CSV (1) gives you a starting file with columns already named to match.
That template also carries smtp_type, imap_type and daily_limit columns, and none of the three is a field this importer maps. Nothing outside the ten required and three optional fields is read. We work out each mailbox’s encryption from the port instead: IMAP 993 is TLS, SMTP 587 is TLS and 465 is SSL, anything else is none. The daily limit is set once for the whole batch, on the review screen.
3

Match your columns, if it asks

Your header names are matched to our fields automatically as soon as the file uploads. When all ten required fields resolve this way, this screen is skipped and you land straight on the review below: Back from there always returns here anyway, so the mapping stays reachable even on a run that skipped it.When something doesn’t resolve, pick the CSV column for each field yourself, from a dropdown per field. Two fields may point at the same column, which is how one password column covers both protocols. Continue stays off until every required field has a column.
4

Review and set sending defaults

The review screen previews the first five rows as they will be mapped, and counts the rows it is about to import. A collapsed panel underneath sets the daily send limit and the random delay between emails every imported account starts with. Change either per account afterwards. The submit button counts the rows in your file, and stays off while an address in it is malformed or repeated, or while the minimum delay is not below the maximum.
5

Watch it import

Submitting uploads the file and queues one job per row. Each job checks that row’s server details and password first, then saves the account and gives it this batch’s sending schedule. The bar moves with rows that have actually finished; the three lines narrated above it advance on a timer and are not a report of where the importer has got to.

​
What happens next

The panel lands on a result screen: a single count when every row went through, or a split of imported against failed when some rows didn’t. Done closes the panel and refreshes Email Accounts, so every account you added is already there.
A row that imports isn’t automatically ready to send. We verify its password and server details on the way in, and a row that fails that check is created anyway: it just lands in Error status rather than Active, the same as a mailbox connected by hand with the wrong details. The wizard’s own success count doesn’t tell the two apart, so check the status column on Email Accounts, not just the result screen. If the run itself fails rather than any single row, you get Import failed and the reason instead of either count, and Back to review puts you back on the review screen with the file still loaded. Sender imports are listed behind the Imports button on Email Accounts, newest first: the ones you ran in this workspace, not your colleagues’, and the most recent rather than all of them. A run that failed outright gets a button on its row, labelled Retry on hover, that starts it again from the file already uploaded. A run that finished with some rows failed gets no such button, so those rows have to go in a fresh file. Retry is refused when the workspace has no credits left, and the subscription prompt opens instead.

​
Troubleshooting

The result screen still counts those as imported: the row was created, we just couldn’t verify it. Either the password or the server details are wrong for that mailbox, or the row carried a tracking domain whose DNS record doesn’t resolve yet, which puts the account in Error on its own even when the mailbox itself answers. Check the status column on Email Accounts after any run, not only the count the import reports, and see Sender statuses.
Failed rows are the ones nothing was created for. The cause you can fix is an address that already belongs to an email account in another workspace: an address can only be an email account in one workspace at a time, so that row is skipped. Remove it from the file, or delete the account from the other workspace first. The run’s failed count sits on its row in the Imports list.
Three different checks block it. On the Match columns screen it’s a required field with no CSV column chosen: fix that in place, by picking a column in that field’s dropdown. On the review screen it’s either an address in your file that isn’t a valid email or repeats another row, or a minimum delay that isn’t below the maximum. The delay you fix in the sending defaults panel; the addresses you can’t fix here, so press Back to Upload (twice, from the review screen), correct the file and add it again.

Add senders: connect, import or managed infrastructure

The routes out of the Add senders panel, what each one gives you, and how to choose between them.

Sender statuses: Active, Paused, Error and the chips

Three states, who can set each one, and the extra chips that outrank the status on a row.

Bulk actions on email accounts

Select several mailboxes and activate, pause, delete or edit their limits, schedule and signature at once.