Outlook / Microsoft 365
Read and send mail via Outlook / Microsoft 365 (Microsoft Graph, OAuth2).
OCNORA ships 0 typed Outlook / Microsoft 365 operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Outlook / Microsoft 365
- Authentication
- OAuth 2.0
- Credential
- the Microsoft {client_id, client_secret, refresh_token} triple
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The refresh token needs read access to what it subscribes to — Mail.Read for messages, Calendars.Read for events, Contacts.Read for contacts. Graph refuses a subscription for a resource the token cannot read. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to an https URL Graph can reach and that answers its validation probe within ten seconds.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with Outlook / Microsoft 365
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Create and send 1
- Send Email
Read and search 1
- Fetch Email
Nodes that use your Outlook / Microsoft 365 connection
Beyond its own nodes, these generic nodes accept your Outlook / Microsoft 365 credential. Each chooses the provider from the connection you select, so the same node also works with the other providers shown.
- Fetch Emailmail.fetchRead the next matching message from a Gmail, Outlook or IMAP inbox.Also works withGmailHostinger Email
- Send Emailmail.sendSend an email through a SendGrid, SMTP, Hostinger, COAX Email API, Outlook or Gmail connection.
A sample Outlook / Microsoft 365 workflow
- 1Mail Eventtrigger.outlook_eventStart a run when a message is created, updated or deleted in an Outlook / Microsoft 365 mailbox.
- 2Fetch Emailmail.fetchRead the next matching message from a Gmail, Outlook or IMAP inbox.
- 3Send Emailmail.sendSend an email through a SendGrid, SMTP, Hostinger, COAX Email API, Outlook or Gmail connection.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Outlook / Microsoft 365 questions
- How does OCNORA authenticate with Outlook / Microsoft 365?
- With a stored OAuth 2.0 credential, shaped the Microsoft {client_id, client_secret, refresh_token} triple. A connection test can check it when you add it.
- What can I automate with Outlook / Microsoft 365?
- 0 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits. The credential also drives 2 generic nodes.
- What if the Outlook / Microsoft 365 operation I need is not listed?
- Where Outlook / Microsoft 365 has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Outlook / Microsoft 365?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Outlook / Microsoft 365 calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Outlook / Microsoft 365 workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.