Automation library · Documents and files

Create mailboxes and aliases on a Mailcow server from a CSV file

Started by someone submitting a form. It calls services over plain HTTP rather than through connectors. 11 steps, 4 loops or waits: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
0Branches: places the flow splits
4Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 7Service 3

The steps in the order they run, from what starts it.

  1. 1On form submissionForm triggerStarts it
  2. 2Get User from CSV-DataExtract From FileService
  3. 3Set JSON-FieldsSetLogic
  4. 4Loop Over Items1Split In BatchesLogic
  5. 5Parse AliasesCodeLogic
  6. 6HTTP Request - MailboxesHttp RequestService
  7. 7Loop Over ItemsSplit In BatchesLogic
  8. 8Wait - MailboxesWaitLogic
  9. 9EndNo OpLogic
  10. 10HTTP Request - AliasesHttp RequestService
  11. 11Wait - AliasesWaitLogic

How it's built

Starts on
Someone submitting a form
Steps
11, 4 loops or waits
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on someone submitting a form.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 11 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 11 steps before you point it at anything that matters.