Fetch IMAP Message
Fetch selected fields for one IMAP message by UID and mailbox reference.
IMAP provider for mailbox listing, search, fetch, and message flag lifecycle.
Connection facts
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.
Action catalog
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
Fetch selected fields for one IMAP message by UID and mailbox reference.
List safe mailbox metadata available to a configured IMAP credential.
Add the IMAP Seen flag to one message by UID after explicit grant.
Remove the IMAP Seen flag from one message by UID after explicit grant.
Search a bounded IMAP mailbox by safe mailbox reference and provider-valid criteria.
Direct answer
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.
Common questions
The current catalog includes 5 IMAP actions across Email Inbox. The exact actions used depend on the workflow and approval rules.
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.