Open and name a workflow

  1. Open Auto Reply → Agents → Visual Builder. New flows start as New workflow; edit the name in the top bar.
  2. Select Incoming email and choose one or more enabled receiving accounts.
  3. Add nodes from the searchable library; select a node to edit its properties.
  4. Connect the incoming trigger to conditions/actions and complete every required branch.
AeroMailer interface: Build an Advance Agent with Visual Builder
Sample-data app screenshot. Select the image to view it at full size; your accounts and content will differ.

Route and chain actions

Conditions can check sender email/domain, subject, body, or contact language. Local actions can add/remove labels, move a message, append a note to an existing contact, update permitted contact fields/Variables, show a desktop notification, wait, apply a business-hours gate, or save scanned attachments. Each organization action continues through Next.

AI classification routes Matched, Not matched, or Uncertain. AI Agent, Rule Agent, Send to email, and Stop are terminal actions. Send to email can forward the incoming message with its original .eml or send a literal custom plain-text subject/body to multiple addresses; see forwarding modes and limits. There is no Webhook or arbitrary script action.

Arrange and edit

Drag supported nodes, zoom/reset the canvas, undo/redo, and use right-click or Shift+F10 for Edit, Clone, Disconnect, Center, or Delete. The single incoming trigger cannot be cloned/deleted. On narrow windows the library and properties become drawers. Use the bottom Test run and Execution history dock to test or inspect runs.

Test flow without sending

Enter sample sender, subject, body, language, and account context; run the dry test and inspect the chosen path. Dry tests do not send email, call a provider, modify contacts, or save real attachments. Test both condition branches and the Uncertain classification path. Validate before enabling. Draft saves may retain unfinished work inactive.

Build with AI and activate

Build with AI appears only when AI Provider is enabled. Describe the workflow, review the generated draft, and apply it to the canvas as an undoable change. Generation does not save or activate the agent and does not select live account IDs for you.

Saving an active workflow assigns it to the selected eligible accounts atomically. Rule-mode conflicts must be resolved; inactive/draft saves do not activate accounts. A workflow or target AI agent can require manual reply approval. Other local/forwarding actions are not gated by that AI-reply approval.

Resume, cancel, and save attachments

Waits and run positions persist across restart while automation eligibility remains valid. Review/cancel runs in History; cancellation cannot undo completed actions or recall sent messages. Saving attachments requires ready, current ClamAV scanning and an approved destination. Missing, unsafe, stale, or incompletely scanned files are not saved. The app must be running for waiting work to resume.

Branch on date and occasion conditions

Use the incoming message date or the matched contact’s birthday or Date variable. Check the comparison, dates, and missing-value branch in the simulator. A matching branch can use the existing actions to send a reply or update a contact field.