Microsoft Power Automate Integration: Calls That Run Your Flows

In a Microsoft 365 shop, everything important starts a flow. Now the phone can too. Abby's virtual receptionists answer 24/7, and every call record can trigger your Power Automate flows: a Teams alert, a SharePoint row, a Planner task, whatever your business runs on.

Start Free Trial →Speak to an Expert Book a Demo

The phone becomes a triggerEvery answered call produces a structured record your flows can act on, the same way a form response or an email already does.

Lands where 365 worksPost the on-call alert in Teams, add the row in SharePoint, create the Planner task. One call can do all three in a single run.

Built by you, in your tenantYour flows, your conditions, your connectors. Abby's job is a complete, consistent record; everything downstream is yours to design.

The Flow Run Your Receptionist Started

ABBY PORTAL · CALL SUMMARY

ANSWERED BY ABBY · 4:47 PM

Hank Sorensen

(612) 555-0176 · 3 min · Known customer

Freezer in Unit 4B is down again; wants a technician tonight; second call this month noted.

UrgentService request

POWER AUTOMATE · FLOW RUN

Trigger · New Abby call record

Condition · Reason contains "urgent" → yes

Action · Post to Teams · On-Call channel

Action · Planner task · send tech to Unit 4B tonight

Action · Add row · SharePoint call log

At 4:47 PM, Hank calls: the freezer in Unit 4B is down again and he needs a technician tonight. Abby answers, captures the unit, the urgency, and the history he mentions, and the finished record triggers your flow. The on-call channel in Teams gets the alert, Planner gets the task, and the SharePoint call log gets its row.

Nobody forwarded a voicemail. Nobody re-typed a sticky note into three systems. The receptionist handled the caller; the flow handled the rest: the division of labor a 365 shop already trusts.

Where The Phone Joins The Microsoft Stack

A Microsoft 365 shop runs on flows because they're visible: every run is logged, every step is inspectable, every rule is written down instead of remembered. The phone has been the exception: calls answered ad hoc, outcomes living in whoever picked up. Abby closes that gap: calls are answered by real receptionists per your instructions, and each one ends as a structured record your flows treat like any other trigger.

The boundary is one-directional by design: call records flow into your tenant; nothing in your tenant reaches back into Abby. Flows can't change your greeting or your transfer rules (those change with your receptionist team), so automation experiments never put your phone line at risk.

Ground Rules For Call-Driven Flows

Trigger on the record, not the ring. Flows start when the call record is complete (caller, reason, summary, outcome), so conditions never evaluate half a conversation.

Let conditions do the triage. Branch on reason, caller status, or time of day before anything posts, and the on-call channel only wakes for on-call problems.

One record, many actions. A single call can post the Teams alert, add the SharePoint row, and create the Planner task in one run, with no human relay in between.

Keep a catch-all branch. End with a default action (a row in the call log), so a call that matches no condition still lands somewhere your team looks.

One direction, always. Records flow from Abby into your tenant; no flow writes back into Abby. Call-handling changes go through your receptionist team, on purpose.

Flows The Front Desk Can Feed

On-call alerts in TeamsAn urgent call matches your condition and the right channel hears about it while the details are still warm.

A SharePoint call log the org ownsEvery record appends to a list your team already reports on: searchable, filterable, governed like the rest of the tenant.

Callbacks as Planner tasksA flow turns "callback promised" into a Planner task with a due date and an owner. The promise survives the afternoon.

Approvals that start on the phoneA caller asks for a refund or a schedule change; your flow routes the captured request into an Approval for the manager to decide.

How It Works

Your onboarding team connects Abby's call records to your Microsoft environment with you and confirms they're arriving.

Abby's receptionists answer 24/7 per your instructions; every call ends as a structured record.

Your Power Automate flows take over: alerting Teams, filing SharePoint rows, creating Planner tasks, or anything else you build.

FAQs

Which answering service works with Microsoft Power Automate?

Abby Connect, an answering service with US-based receptionists and an AI receptionist option, whose call records can trigger the Power Automate flows you build in your own tenant.

Can a flow change how Abby handles my calls?

No. Data moves one way: from Abby into Microsoft 365. Greetings, screening, and transfer rules change with your receptionist team, never through automation.

What Microsoft 365 apps can a call reach?

Anything your flows connect: Teams, SharePoint, Planner, Outlook, Excel, Approvals, and the rest of the connector library your tenant already uses.

Do we need Power Automate to get Abby summaries in Teams?

No. Abby has a native Microsoft Teams integration your onboarding team sets up for you. Power Automate is for the logic you want to own: conditions, multi-step actions, and destinations beyond the defaults.

Who builds and maintains the flows?

You do, and that's the point. Your flows live in your tenant under your policies. Onboarding confirms records are arriving and can point you in the right direction; the logic stays yours.

Related Integrations

Use a tool we haven’t listed?

We build missing integrations for new customers during onboarding, free. Tell us what you run on and we’ll connect it.

Schedule a Call Call 877-303-5757