Back to apps
Microsoft Outlook logo
CommunicationPlanned

Microsoft Outlook × Volimox

Keep email, contacts, and customer follow-up inside Microsoft 365.

Best for Microsoft 365 teams and operations desks.

Connection boundary

Volimox only takes the permissions this workflow needs. The account owner reviews access before anything is activated.

Request a pilot
01

Special workflows for Microsoft Outlook.

Each scenario shows the trigger, the Volimox handoff, and the human checkpoint. These are concrete workflow blueprints, not a claim that every connection is live today.

Use case 01Microsoft Outlook × Volimox

Email to Microsoft 365 intake task

Convert a customer email into an accountable operations task.

Starts when

A new Outlook email arrives in the monitored service or dispatch inbox.

Result

An inbox request becomes a visible task with a clear owner and next step.

Volimox workflow

  1. 01Volimox extracts the request, urgency, preferred time, and contact details.
  2. 02Volimox creates a structured lead and assigns the task to the right Microsoft 365 owner.
  3. 03The owner reviews the brief and chooses the next customer or dispatch action.

Human checkpoint

Required fields and ownership are checked before the task is considered ready.

Use case 02Microsoft Outlook × Volimox

Status change to controlled email

Send a consistent customer update when a job or booking moves forward.

Starts when

A quote, appointment, or dispatch status changes in Volimox.

Result

Every customer update is traceable to the workflow event that caused it.

Volimox workflow

  1. 01Volimox loads the approved Outlook template for that status.
  2. 02Volimox inserts only the verified customer and booking fields.
  3. 03The team member approves the message and the activity is recorded against the lead.

Human checkpoint

An authorized team member remains responsible for the final send.

02

Supported triggers and actions.

A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.

Triggers

  • New email
  • New contact
  • New calendar event

Actions

  • Send email
  • Create draft
  • Create contact
  • Create calendar event
03

Detailed connection code.

This server-side TypeScript reference follows the same connection → action → mapped input pattern used by modern automation platforms. Provider credentials remain inside the approved connection; browser code never receives them.

TypeScript · server only

Send a Microsoft 365 update

Copy-ready reference
import { createZapierSdk } from "@zapier/zapier-sdk"

const zapier = createZapierSdk({
  apiKey: process.env.ZAPIER_API_KEY,
})

export async function runMicrosoftOutlookAction() {
  const { data: connection } = await zapier.findFirstConnection({
    app: "microsoft-outlook",
    owner: "me",
  })

  if (!connection) {
    throw new Error("No approved Microsoft Outlook connection was found")
  }

  const result = await zapier.runAction({
    app: "microsoft-outlook",
    action: "send_email",
    connection: connection.id,
    input:
    {
      "to": "customer@example.com",
      "subject": "Booking status update",
      "body": "Your requested time is being reviewed.",
      "conversationId": "{{lead.outlookConversationId}}"
    },
  })

  return result.data
}
Action identifiers and available fields can vary by provider account, connector version, and plan. Validate the selected action in a sandbox connection before production activation.
04

Connection setup.

The setup path is specific to the provider. We will never ask you to paste credentials into a public page.

Microsoft OAuth

A reviewable connection, step by step.

  1. 01Microsoft Entra admin consent
  2. 02Select the Microsoft 365 mailbox
  3. 03Choose calendar and mail scopes
Planned

This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.

Tokens and provider credentials belong in the authenticated connection console, never in this public page.
Request a pilot

Related apps

Common handoffs with Microsoft Outlook.

Provider names and logos belong to their respective owners. Volimox only uses them to describe connection possibilities and configured workflows.