
Step 1: Connect your stack
27+ native integrations plus 9,800+ tools via managed connectors. Mostly one-click OAuth, a few API keys. No webhooks, no Zapier zaps.
Viktor works in Microsoft Outlook Email for you. Ask in Slack or Microsoft Teams.
Viktor is an AI employee that connects to Microsoft Outlook Email and helps you stay on top of your inbox and get replies out, running 26 Microsoft Outlook Email actions for you like Send Email, Get Folder, and Find Email. Ask in plain English from your workspace; Viktor does the work in Microsoft Outlook Email and reports back. Viktor connects in one click via OAuth.
Viktor connects to your Microsoft Outlook Email account and completes work in it. He doesn't just answer questions about Microsoft Outlook Email, he takes the actions on your behalf and delivers the finished result to your workspace.
Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Microsoft Outlook Email actions, chains them with the other 9,800+ tools he connects to, and asks for approval before anything sensitive runs.
About Microsoft Outlook Email
Microsoft Outlook lets you bring all your email accounts and calendars in one convenient spot.
Message Viktor in a Slack channel, a Microsoft Teams chat or a direct message. He opens Microsoft Outlook Email, does the work and posts the result in the same thread, so nobody has to switch tabs.
He can also run Microsoft Outlook Email work on a schedule, like a weekly Microsoft Outlook Email summary posted to your team's channel. Anything sensitive waits for your approval before it runs.
Viktor is not affiliated with or endorsed by Microsoft Outlook Email.
You ask in your workspace
Describe what you need in plain English
Viktor picks the actions
Selects from 26 Microsoft Outlook Email actions, chains them together
Runs in Microsoft Outlook Email
Helps you stay on top of your inbox and get replies out - your real data.
Reports back
Delivers the finished result to your workspace
Messages you'd actually send. Paste one into your workspace, swap in your specifics, and Viktor takes it from there.
“Summarize everything new in Microsoft Outlook Email from the last 24 hours and flag what needs a reply.”
— you, to @Viktor
“Draft a reply to the latest Microsoft Outlook Email thread about the renewal and send it after I approve.”
— you, to @Viktor
“Search Microsoft Outlook Email for the conversation about the Q3 launch and pull out the action items.”
— you, to @Viktor
“Watch Microsoft Outlook Email for anything mentioning invoices and log it in a sheet every Friday.”
— you, to @Viktor

27+ native integrations plus 9,800+ tools via managed connectors. Mostly one-click OAuth, a few API keys. No webhooks, no Zapier zaps.
Message Viktor like a teammate: "Pull this week's MRR from Stripe." "Triage new Linear bugs." "Pause Meta ads over $40 CPA." Any tool.
Viktor opens the tools, runs the work, and posts back exactly what changed. Sensitive actions wait for your approval. It’s all logged.
Ask in plain English from your workspace. Viktor picks the right Microsoft Outlook Email actions, runs the work, and reports back. No workflows to build.
Update an existing contact.
Send a new email, reply to an existing message, or save a draft — all in one tool. Omit inReplyToMessageId to send a new email. Provide inReplyToMessageId to reply to an existing message (threads correctly). Set isDraft: true to save to Drafts instead of sending immediately. Attach files by passing URLs or /tmp paths to files. Example (send new): send-email(recipients=["you@example.com"], subject="Hello", content="Hi there") Example (reply): send-email(inReplyToMessageId="AAMk...", content="Thanks for your note") Example (draft): send-email(recipients=["boss@example.com"], subject="Weekly report", content="...", isDraft=true) Use Find Email to locate a message id before replying.
Create or update an Outlook contact (upsert). Omit contactId to create a new contact; provide contactId to update an existing one. Use Find Contacts first to look up a contact's id before updating. Example (create): save-contact(givenName="Cosmo", surname="Kramer", emailAddresses=["kramer@kramerica.com"]) → creates contact, returns new contact object with id. Example (update): save-contact(contactId="AQMk...", businessPhones=["+1-555-0100"]) → patches the existing contact. See the create documentation See the update documentation.
Reply to an email in Microsoft Outlook.
Removes a label/category from an email in Microsoft Outlook.
Moves an email to the specified folder in Microsoft Outlook.
Apply one or more state mutations to an email message: mark read/unread, add/remove categories, move to a folder, or change the flag status. All params except messageId are optional — only the ones you provide are applied. Use Find Email to obtain a message id before modifying. Recipes: Mark read: isRead: true | Mark unread: isRead: false Add category: addCategories: ["Follow Up"] | Remove category: removeCategories: ["Follow Up"] Move to archive: destinationFolderId: "archive" | Move to inbox: destinationFolderId: "inbox" Flag: flagStatus: "flagged" | Unflag: flagStatus: "notFlagged" | Mark complete: flagStatus: "complete".
Retrieves mail folders from a shared or delegated mailbox (routes to /users/{userId}/mailFolders). Returns { count, folders } where folders contains each folder's id, displayName, parentFolderId, childFolderCount, totalItemCount, and unreadItemCount. The count field reflects the true API total when Microsoft Graph returns @odata.count; when Include Subfolders is true or Graph does not return @odata.count for the requested filter, count equals the number of folders actually retrieved. Use this action to resolve a shared mailbox folder display name to its ID — set Display Name to filter by exact name. Use Get Shared Folder instead when you already have the folder ID.
Get all the labels/categories that have been defined for a user.
Ask for outcomes that span tools - Viktor pulls from Microsoft Outlook Email, cross-references the rest of your stack, and delivers one finished result.
Yes. Microsoft Outlook Email is one of the 9,800+ tools Viktor connects to, in one click via OAuth. Once connected, anyone on your team can put Viktor to work in Microsoft Outlook Email from their workspace - no workflow builder, no code.
Ask Viktor in your workspace to connect Microsoft Outlook Email, then approve the one-click OAuth prompt. Viktor never sees your password, handles authentication itself, and starts working right away. Setup takes about two minutes, and you can revoke access at any time.
Viktor can run 26 Microsoft Outlook Email actions, including Send Email, Get Folder, and Find Email - and chain them with other tools in a single request. In practice that means Viktor helps you stay on top of your inbox and get replies out. If a task spans several actions, Viktor plans the sequence itself and reports back when the work is done.
No. Viktor isn't a workflow builder - there are no triggers to map and nothing to maintain. You ask for the outcome in plain English in your workspace, and Viktor decides which Microsoft Outlook Email actions to take, runs them, and reports back.
Start free. Viktor delivers.
Start for free today. No credit card required.