Microsoft 365 + any website
Read a table, a price or a listing on the page you're on and send it to Microsoft 365.
Use Microsoft 365 in workflows that start from the page you're on — straight from your browser to Microsoft 365, nothing in between.
Each action is a node you drop on the canvas. Pair it with any of the 10 triggers — a schedule, a right-click, a page change.
Example actions · Full list in the docs
Read a table, a price or a listing on the page you're on and send it to Microsoft 365.
Classify, summarise or rewrite with a model that runs in your browser before it reaches Microsoft 365.
No published templates use Microsoft 365 yet. Docs recipe ↗
Register a small app once in the Google Cloud console or Microsoft Entra (Azure portal), with the redirect URI the AWFlow credential form shows you.
Add a Microsoft 365 credential in AWFlow and paste the Client ID. A Google Web application client also needs its Client Secret; Microsoft 365 needs none.
Approve access in the vendor's own window. Tokens go straight from the vendor to your browser and never pass through AWFlow's servers.
No. When a step runs, your browser sends the request to Microsoft 365. AWFlow's servers never relay the call.
No. Local mode works without an account and keeps the Microsoft 365 credential in this browser. Signed in, you choose per credential: this browser or your account. Installing a template from the Marketplace needs sign-in.
No. Workflows run while your browser is open. A Wait of a minute or more in the extension survives closing the tab and picks up where it left off, for up to 30 days.
No. Workflows run in your browser, so there are no per-task fees. Microsoft 365 applies its own usual limits.