Bridging Outlook and Power Automate with a Custom Add-In
An in-home care provider had built Power Automate flows to handle repetitive admin, but staff still had to leave Outlook to trigger them. A custom Outlook Online add-in closed the gap - one click from an email to the right flow, documents processed automatically.
The Situation
A community nursing provider - running in-home care services and care advisory across their client base - had done the hard work most businesses skip. They’d already built Power Automate flows to handle the repetitive admin that comes with coordinating care: processing documents, updating records, routing approvals, generating correspondence.
The flows worked. But there was a gap.
Staff still lived in Outlook. Client communications, referrals, care plan updates, compliance paperwork - everything arrived as email, and most of it needed to flow through one of the automations the team had already built. But triggering a flow meant leaving Outlook, opening Power Automate, finding the right flow, and kicking it off manually. Then going back to the email to mark it done.
The automation existed. The context-switching killed the productivity gain.
They asked us to close the loop - to make the flows feel like a natural part of the inbox, not a separate tool staff had to remember to use.
What We Built
We built a custom Outlook Online add-in that surfaces the team’s Power Automate flows directly in the email interface.
Staff select an email, open the add-in, and see the list of flows they’re permitted to run. One click triggers the right flow with the email and its attachments passed through automatically. Documents get processed, records get updated, approvals get routed - and the staff member stays in Outlook the entire time.
Key design choices:
Permissions-aware flow list - each user only sees the flows they’re allowed to run. No clutter, no mistakes, no “is this the one I’m meant to use?”
Context-aware triggers - the email content, attachments, and metadata pass straight into the flow, so there’s no copy-paste and no risk of the wrong document being processed.
No workflow rebuild required - the add-in wraps the existing Power Automate flows rather than replacing them. All the automation logic the team had already built stayed exactly where it was; the add-in just gave it a new entry point.
The Result
One click from an email to a completed workflow.
The gap between “email arrives” and “automation runs” closed from a multi-step context switch to a single action. Staff stay in the tool they already use all day. The Power Automate investment the team had already made finally felt like the productivity tool it was supposed to be.
Document processing, record updates, and approval routing now happen as a natural extension of reading email - not as a separate task competing for attention.
For a team managing the coordination load of community nursing - where responsiveness directly shapes client outcomes - taking friction out of every single email interaction adds up fast.
