IMAP provider for mailbox listing, search, fetch, and message flag lifecycle.

5 listed actions1 capability groups

Connection facts

What the IMAP connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
imap-password
Setup
IMAP is a protocol, not one vendor. Use the mailbox provider's IMAP settings or app-password page, then enter host, port, TLS mode, username, and password in StackOS.
Capability groups
Email Inbox
Action boundaries
3 read actions2 write actions

Action catalog

Actions listed for IMAP.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

5 matching actions

Email InboxReads data

Fetch IMAP Message

Fetch selected fields for one IMAP message by UID and mailbox reference.

Email InboxReads data

List IMAP Mailboxes

List safe mailbox metadata available to a configured IMAP credential.

Email InboxCan make changes

Mark IMAP Message Seen

Add the IMAP Seen flag to one message by UID after explicit grant.

Email InboxCan make changes

Mark IMAP Message Unseen

Remove the IMAP Seen flag from one message by UID after explicit grant.

Email InboxReads data

Search IMAP Messages

Search a bounded IMAP mailbox by safe mailbox reference and provider-valid criteria.

Direct answer

How does the IMAP integration work?

People continue using IMAP as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03IMAPDoes its bounded part
  4. 04Checked resultKeeps the proof

Common questions

IMAP and StackOS.

What can the IMAP integration do in StackOS?

The current catalog includes 5 IMAP actions across Email Inbox. The exact actions used depend on the workflow and approval rules.

Does StackOS replace IMAP?

No. IMAP remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.