Clean Up IMAP Evidence Export
Email InboxCan make changes
Delete one completed IMAP evidence staging transfer by its opaque transfer id only.
IMAP provider for mailbox listing, search, metadata fetch, bounded evidence staging, and message flag lifecycle.
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 actions4 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.
7 matching actions
Export IMAP Message Evidence
Email InboxCan make changes
Stage one exact IMAP RFC822 message and bounded attachments for a host-owned evidence backend without acknowledging the message.
Fetch IMAP Message
Email InboxReads data
Fetch selected parsed fields from a bounded MIME prefix by UID. Inspect content_completeness for byte and field truncation; use imap.message.export for complete original MIME and attachment evidence.
List IMAP Mailboxes
Email InboxReads data
List safe mailbox metadata available to a configured IMAP credential.
Mark IMAP Message Seen
Email InboxCan make changes
Add the IMAP Seen flag to one message by UID after explicit grant.
Mark IMAP Message Unseen
Email InboxCan make changes
Remove the IMAP Seen flag from one message by UID after explicit grant.
Search IMAP Messages
Email InboxReads data
Search one bounded UID page and report matched_count, has_more and next_after_uid. Continue with unchanged mailbox and criteria plus after_uid and the returned UIDVALIDITY as expected_uidvalidity.
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.
- 01Your requestStart in your AI
- 02StackOS planExpands the steps
- 03IMAPDoes its bounded part
- 04Checked resultKeeps the proof
More from Communications
Related integrations.
Communications
Local Agent Chat
StackOS local conversation surface for direct human-to-agent messages, rich response blocks, and interaction events.
Communications
Slack Bot
Slack Web API provider for bot identity, message sends, conversation discovery, membership sync, and signed HTTP ingress.
Messaging
Communications
SMTP
SMTP provider for send-only email. Acceptance by the SMTP server is not delivery or read confirmation.
Email Send
Common questions
IMAP and StackOS.
What can the IMAP integration do in StackOS?
The current catalog includes 7 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.