Special workflows for Microsoft Outlook Calendar.
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.
Request to Microsoft 365 calendar hold
Create a tentative dispatch window after the intake has enough information.
Starts when
A Volimox request passes the configured service, location, and time rules.
Result
Microsoft 365 scheduling reflects the actual state of the customer request.
Volimox workflow
- 01Volimox checks the selected Outlook calendar for available windows.
- 02Volimox creates a tentative event with the customer and job context.
- 03The operator confirms the hold or selects another window for the customer.
Human checkpoint
The event remains tentative until the responsible operator confirms it.
Schedule change to notification
Keep a customer informed when the assigned time moves.
Starts when
An Outlook event is updated or canceled for a linked Volimox booking.
Result
A schedule change creates one visible customer follow-up instead of confusion.
Volimox workflow
- 01Volimox compares the new time and status with the last known workflow state.
- 02Volimox prepares a concise change notice with the next available action.
- 03The operator approves the message and the timeline records the change.
Human checkpoint
Stale or unrelated calendar changes do not send a customer message.
Supported triggers and actions.
A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.
Triggers
- Event created
- Event updated
- Event canceled
Actions
- Find availability
- Create event
- Update event
- Cancel event
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
Create an Outlook calendar hold
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runMicrosoftOutlookCalendarAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "microsoft-outlook",
owner: "me",
})
if (!connection) {
throw new Error("No approved Microsoft Outlook Calendar connection was found")
}
const result = await zapier.runAction({
app: "microsoft-outlook",
action: "create_event",
connection: connection.id,
input:
{
"calendarId": "{{env.OUTLOOK_CALENDAR_ID}}",
"subject": "Tentative: {{lead.service}}",
"start": "{{lead.requestedStartIso}}",
"end": "{{lead.requestedEndIso}}",
"attendees": "{{lead.email}}"
},
})
return result.data
}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.
- 01Microsoft Entra admin consent
- 02Select calendars
- 03Set timezone and working hours
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps