# How to Get a Shared Phone Alert for a New OneDrive File

> Use OneDrive for Business and one protected Power Automate action to send a fixed, replay-safe Ping without exposing file details.

- Published: 2026-11-05
- Author: PingRoom
- Category: Automation
- Topics: OneDrive new file notification, OneDrive phone alert, Power Automate OneDrive alert, webhook push notifications
- Canonical: https://pingroom.io/blog/onedrive-new-file-push-notifications
- Cover image: https://pingroom.io/blog/onedrive-new-file-push-notifications-cover.webp
- Cover description: Two PingRoom avatars and Pingo watch one blank file tile move from a miniature cabinet into a terracotta signal dish.

If one person needs OneDrive activity notifications, start with Microsoft's own file-sharing or SharePoint alert options. If the same new-file signal should reach a small group, use **OneDrive for Business → When a file is created (properties only)** in Power Automate, then post fixed copy to a PingRoom incoming webhook.

Use the OneDrive file `Id` as the `Idempotency-Key`. That gives retries and duplicate flow runs for the same file one stable identity without putting the filename, path, uploader, or file contents on anyone's lock screen.

This is a Power Automate webhook recipe, not a native OneDrive integration.

## Choose the smallest notification path

| Need                                                             | Start here                                                                 |
| ---------------------------------------------------------------- | -------------------------------------------------------------------------- |
| Know when someone views or edits one shared Office file          | Use the notification bell in OneDrive's **Manage access** view             |
| Get email or SMS for changes in a SharePoint-backed library      | Use the organization's approved SharePoint alert or rule                   |
| Send one fixed new-file signal to a stable small group           | Use the OneDrive for Business trigger, Power Automate, and a PingRoom Room |
| Review filenames, ownership, versions, or file contents          | Keep that work in OneDrive or the document workflow that owns it           |
| Require audit history, escalation, or guaranteed acknowledgement | Use a governed document or incident workflow built for that requirement    |

Microsoft's [shared-file support page](https://support.microsoft.com/en-gb/onedrive/see-files-you-shared-in-onedrive) describes notifications for views or edits on a selected shared Office file. That is a different job from telling the same small group that one folder received a new file.

## Check the plan and trigger boundaries

You need:

- a OneDrive for Business account and permission to read the selected folder;
- a Power Automate environment where the external **HTTP** action is available under your license and tenant policy;
- a private PingRoom Room whose owner has active **PingRoom Pro**, because incoming webhooks are a Pro connection;
- Room members who have allowed PingRoom notifications on their devices.

Microsoft lists the [OneDrive for Business connector](https://learn.microsoft.com/en-us/connectors/onedriveforbusinessconnector/) as Standard. The HTTP action used to call an external webhook is a premium capability in many Power Automate environments. Check the action in your designer and confirm the flow's plan before building the rest of the workflow.

Use **When a file is created (properties only)**, not the full-content trigger. The Room needs the event identity, not the file bytes. Microsoft's connector reference says that files moved within OneDrive are not considered newly created files. It also warns that trigger behavior can produce more than one run in some cases, which is why the file identity matters.

## Create one privacy-minimal Ping

Use fixed copy:

- **Title:** `New OneDrive file`
- **Message:** `A new file is ready in the shared folder`

The message tells the group where to look without exposing the document on a lock screen. OneDrive remains the source of truth for the filename, path, uploader, permissions, version, and content.

Open the destination Room in [PingRoom's browser app](/app/rooms), then go to **Settings → Connections → From another app**.

1. Add an incoming webhook named **OneDrive**.
2. Keep **Quick Ping** on **Custom message**.
3. Choose a recognizable icon, color, and sound.
4. Save it and copy the complete webhook URL into protected flow configuration.

The URL contains the credential that can post into the Room. Do not put it in a flow description, screenshot, shared template, chat message, or client-side script. If it leaks, regenerate the PingRoom secret and update the flow.

The [incoming-webhook walkthrough](/blog/webhook-to-push-notification) explains the Room setup and response. The [webhook reference](/documents/webhooks) carries the current limits, cooldown, errors, and retry behavior.

## Configure the OneDrive trigger

Create an automated cloud flow in Power Automate.

1. Select **OneDrive for Business**.
2. Choose **When a file is created (properties only)**.
3. Select one folder.
4. Leave **Include subfolders** off unless the Room should receive the same signal for every descendant folder.
5. Test the trigger with one harmless blank file.

The trigger returns blob metadata that includes `Id`, the connector's unique identifier for the file or folder. Do not substitute the filename. Two different folders can contain the same filename, and a filename can change.

## Send the fixed Ping

Add an **HTTP** action after the trigger and use this field map:

| HTTP field               | Value                                            |
| ------------------------ | ------------------------------------------------ |
| Method                   | `POST`                                           |
| URI                      | the protected PingRoom webhook URL               |
| Header `Accept`          | `application/json`                               |
| Header `Content-Type`    | `application/json`                               |
| Header `Idempotency-Key` | dynamic content **Id** from the OneDrive trigger |

Use this fixed body:

```json
{
  "title": "New OneDrive file",
  "message": "A new file is ready in the shared folder"
}
```

Do not add the filename, path, uploader, file URL, or file contents. Keep the body unchanged when the action retries.

Open the HTTP action's settings and enable **Secure Inputs** and **Secure Outputs**. Those controls reduce accidental exposure in ordinary run history. They do not protect the URL from everyone who can edit the flow, so keep the editor list narrow.

![Two PingRoom avatars compare two matching blank file tokens at a wooden duplicate gate while Pingo watches one repeated signal stay behind the divider.](/blog/onedrive-new-file-push-notifications-1.webp)

[Pingo the Pigeon](/Pingo), PingRoom's official mascot and fictional Chief Marketing Officer, is inspecting the duplicate gate with his usual restraint. He cannot read the folder, flow, webhook URL, Room, or phone. People configure the workflow and remain responsible for its permissions and copy.

_AI-generated editorial artwork uses approved Pingo and PingRoom avatar references. The miniature mechanism is an illustrative example, not a customer setup or product screen._

## Read the replay rule correctly

The connector may start more than one flow run for the same source change. If every run sends the same body with the same file `Id`, PingRoom can return the original completed response instead of creating another Ping.

That protection is bounded:

- PingRoom stores completed idempotency receipts durably for at least one hour.
- Reusing one key with changed copy returns `409 idempotency_conflict`.
- A different OneDrive file has a different `Id` and should create a new Ping.
- A new key is still subject to the webhook's cooldown, which is five seconds by default.

If several files can arrive together, do not turn each one into an interruption. Batch the intake in the source workflow, use a digest, or route the group to OneDrive. PingRoom is the attention signal, not the folder index.

## Test five boundaries

Use a test folder, private test Room, and non-sensitive files.

1. **New file:** create one blank file and confirm that the flow sends one Ping with the fixed title and message.
2. **Exact replay:** resend the same HTTP request with the same file `Id` and unchanged body within an hour. Confirm that Room history still contains one Ping for that file.
3. **Changed body:** in a controlled test, reuse that file `Id` with changed copy and confirm PingRoom returns `409` instead of silently creating a different event.
4. **Second file:** create another blank file and confirm its different `Id` creates one new Ping.
5. **Move and privacy:** move an existing file into the folder and inspect the flow history. The connector contract says a move is not a new-file event. Also lock a test phone and confirm that no filename, path, uploader, or link appears.

Our recorded verifier runs the documented request against a local PingRoom mock. It passed first acceptance, exact replay, changed-body conflict, a second file identity, and a disabled-webhook failure. It did not use a live Microsoft tenant, OneDrive folder, PingRoom Room, or phone, so the harmless end-to-end test still belongs in your environment.

HTTP `200` with `success: true` means PingRoom accepted the event or returned the completed response for that key. It does not prove that every member saw the notification. Connectivity, operating-system permissions, Focus modes, Room settings, and device state still affect display.

When the five checks pass, [create or choose the destination Room](/app/rooms) and enable the flow for one folder. Keep document details and history in OneDrive; let the Room carry only the moment the group needs to notice.

_The two editorial illustrations were created with AI using approved PingRoom character references and reviewed by the PingRoom team._