Power Automate SharePoint File Teams Alert — 5 Simple Steps

What You’ll Build

A Power Automate SharePoint file Teams alert is one of the most useful automations you can set up for any team that shares documents. Every time someone uploads a new file to a SharePoint document library, your flow will instantly post an alert in a Microsoft Teams channel — complete with the file name and a direct clickable link. No manual announcements, no missed uploads.

This is also the first flow in the series that connects two Microsoft 365 apps together: SharePoint and Microsoft Teams. If you have completed Flows 1 and 2, you already know the building blocks. This flow combines them.

What You’ll Learn

• How to set up a Power Automate SharePoint file Teams alert using an automated trigger
• How to use dynamic content to pull live file details — name and link — directly from SharePoint
• How to use a Compose action to shape your message before sending it
• How to post a formatted notification to a Teams channel with a clickable file link
• How Power Automate connects two different Microsoft 365 apps in a single flow

Why a Power Automate SharePoint File Teams Alert Works

How many times have you uploaded an important file to SharePoint and then had to go into Teams to tell everyone about it? Or worse — how many times has someone uploaded a file and nobody noticed for days?

A Power Automate SharePoint file Teams alert closes that gap permanently. The moment a file lands in your document library, your Teams channel knows about it. Your team sees the file name and a direct link — without anyone needing to say a word. This is especially useful for shared project folders, contract libraries, report repositories, or any document library where your team needs to stay in sync.

This is also an important milestone in your Power Automate journey. You are moving from single-app flows to multi-app automation — the pattern that powers most real-world Power Automate solutions.

Prerequisites

Before you start, make sure you have the following in place:

• Microsoft 365 licence — Any plan that includes Power Automate (such as Microsoft 365 Business Basic, Standard, or Premium). No premium licence is needed for this flow.
• SharePoint document library — An existing SharePoint site with a document library. Note down:
  • The full URL of your SharePoint site (for example: https://yourcompany.sharepoint.com/sites/ProjectDocuments)
  • The name of the document library (for example: Documents or Project Files)
• Microsoft Teams channel — A Teams channel where alerts will be posted. Note down the team name and channel name.
• Permissions — At minimum Contribute access to the SharePoint library and Member access to the Teams channel.
• Power Automate access — Sign in at make.powerautomate.com using your Microsoft 365 work or school account.

What is a document library? A SharePoint document library is a cloud-based folder designed to store and manage files. It comes with built-in features like version history, access controls, and metadata columns. Every SharePoint site includes a default library called Documents.

Step-by-Step: Building the Power Automate SharePoint File Teams Alert

Step 1 — Create a New Automated Cloud Flow

1. Go to make.powerautomate.com and sign in.
2. In the left-hand menu, click Create.
3. Click Automated cloud flow. This type of flow starts automatically when something happens — in this case, when a new file is created in SharePoint.
4. In the panel that appears:
   • Flow name: Type New SharePoint File Teams Alert
   • In the Choose your flow’s trigger search box, type When a file is created
   • From the results, select When a file is created (properties only) under the SharePoint section.
5. Click Create.

Why “properties only”? There are two SharePoint file triggers available. The properties only version gives you the file’s metadata — name, link, created date — without downloading the file itself. This is faster and all you need for a Teams alert. Avoid the “created or modified” variant — it fires on every edit too, which would flood your Teams channel every time someone saves a change to an existing file.

Step 2 — Configure the SharePoint Trigger (Trg_NewSPFile)

After clicking Create, the flow designer opens with the SharePoint trigger card already added.

1. Click on the trigger card to expand it.
2. Rename the trigger: click the three dots (…) in the top-right corner of the card, click Rename, type Trg_NewSPFile, and press Enter. Trg stands for Trigger.
3. Configure the following fields:
   • Site Address: Click the dropdown and select your SharePoint site. If it does not appear, click Enter custom value and paste the full site URL.
   • Library Name: Click the dropdown and select the document library you want to monitor (for example, Documents or Project Files).

Your trigger is now set. Power Automate will watch this library and start the flow the moment a new file is uploaded.

Step 3 — Add a Compose Action to Build the Message (Cmp_BuildFileLink)

The trigger captures the file name and a direct link. Before posting to Teams, use a Compose action to assemble the full message. This keeps your flow clean and easy to update later without touching the Teams action directly.

1. Click + New step below the trigger.
2. In the search box, type Compose. Under the Data Operation section, click Compose.
3. Rename this action: click the three dots (…), select Rename, type Cmp_BuildFileLink, and press Enter. Cmp stands for Compose.
4. Click inside the Inputs field and build your message using dynamic content:
   • Type: 📄 New file uploaded:
   • Click Add dynamic content and select Name from the Trg_NewSPFile section. This inserts the actual file name at run time.
   • Press Enter for a new line, then type: 🔗 Open file:
   • Click Add dynamic content again and select Link to item. This inserts the direct SharePoint URL to the file.

Your Compose Inputs field should now look like this:

📄 New file uploaded: [Name]
🔗 Open file: [Link to item]

Where [Name] and [Link to item] are blue dynamic content tokens — not typed text.

What is dynamic content? Dynamic content is live data captured from a previous step when the flow runs. When a new file is uploaded, the trigger records the file name, upload date, uploader, and a direct link. Inserting a dynamic content token means the real value — such as the actual file name — replaces the token every time the flow runs.

Step 4 — Add the Teams Post Action (Ntf_PostTeamsFileAlert)

1. Click + New step below the Compose action.
2. In the search box, type Post message in a chat or channel. Under the Microsoft Teams section, click Post message in a chat or channel.
3. Rename this action: click the three dots (…), select Rename, type Ntf_PostTeamsFileAlert, and press Enter. Ntf stands for Notification.
4. Configure the following fields:
   • Post as: Select Flow bot. The message will appear in Teams as sent by Power Automate.
   • Post in: Select Channel.
   • Team: Select the team where you want the alert posted.
   • Channel: Select the channel (for example, General or Project Updates).
   • Message: Click inside the Message field, click Add dynamic content, and under the Cmp_BuildFileLink section select Outputs. This inserts the full message you composed in Step 3.

Why route through Compose first? Using a Compose action separates the building of the message from the sending of it. This makes your Power Automate SharePoint file Teams alert easier to read, test, and update — especially as flows grow more complex over time.

Step 5 — Save and Test Your Flow

1. Click Save in the top-right corner.
2. Open SharePoint in a new browser tab, navigate to the document library in the trigger, and upload any test file (a simple .txt or .docx works).
3. Switch back to Power Automate. Within 1–3 minutes a new run will appear in the 28-day run history at the bottom of the flow designer.
4. Check your Teams channel — the alert should appear with the file name and a clickable link.

Why does it take a minute or two? Event-based flows triggered by SharePoint can take 1–3 minutes to fire after a file is uploaded. This is normal — Power Automate polls SharePoint on a schedule. For most team workflows this short delay is perfectly acceptable.

Tips and Customisation

Adding the Uploader’s Name

In your Cmp_BuildFileLink action, add a new line and insert the dynamic content token Created By DisplayName. Your alert will then include something like: Uploaded by: Vishnu Rajan.

Filtering Alerts by Folder

If your library has multiple folders and you only want alerts for files in a specific one, add a Condition action between the trigger and the Compose step. Check whether the Folder path token contains the folder name you want, and only continue to the Teams post if that condition is true.

Sending Different Alerts Based on File Type

Want PDF uploads to go to one channel and Word documents to another? Add a Condition action that checks whether the Name token ends with .pdf or .docx and route each to a different Teams channel.

Common Mistakes to Avoid

• Using the wrong trigger — Always select When a file is created (properties only), not “created or modified.” The modified version fires on every file save, which will flood your Teams channel with repeated alerts for the same file.
• Link not clickable in Teams — The Link to item token outputs a plain URL. Teams renders these as clickable links automatically. If the link is not working, check for extra spaces or stray characters around the token in your Compose action.
• Flow not triggering after upload — Wait 3 minutes, then check the run history. If there is still no run: confirm you uploaded to the exact library selected in the trigger, check the flow is switched on, and verify you have at least Contribute access to the SharePoint library.
• SharePoint site not in the dropdown — Your Power Automate account does not have access to that site. Contact your SharePoint site owner to request access.
• Compose Outputs not appearing in dynamic content — Click See more in the dynamic content panel. Make sure the Compose action is saved and named before you move on to the Teams step.

How to Export This Flow as a Solution

1. In Power Automate, click Solutions in the left-hand menu.
2. Click New solution. Name it Flow 3 – SharePoint File Teams Alert, set a publisher, and click Create.
3. Inside the solution, click Add existing → Automation → Cloud flow.
4. Select your New SharePoint File Teams Alert flow and click Add.
5. Click Export → Export as zip. Save the .zip file to your computer.
6. To import into another environment, go to Solutions → Import solution → upload the .zip file and follow the prompts to reconnect both the SharePoint and Teams connections.

Download the sample flow: A ready-to-import solution package for this flow is available for download below. Import it, update the SharePoint site, library, Teams team, and channel settings to match your environment, and you are ready to go.

Download the Solution from GitHub

All sample flows in this series are available as ready-to-import solution packages on GitHub. You do not need a GitHub account to download them — just click the link, download the .zip file, and import it directly into Power Automate.

1. Visit the Power Automate Beginner Series GitHub repository.
2. Find the folder for this flow and click the .zip solution file.
3. Click Download raw file to save it to your computer.
4. In Power Automate, go to Solutions → Import solution.
5. Upload the .zip file and follow the prompts. When asked to set up connections, sign in with your Microsoft 365 account to authorise both SharePoint and Teams.
6. Once imported, open the flow and update the Site Address, Library Name, Team, and Channel fields to match your own environment.
7. Save and test by uploading a file to your SharePoint library — the Teams alert should fire within a couple of minutes.

Note: The solution is provided as-is for learning purposes. Connection references will need to be configured for your own Microsoft 365 tenant after import. If you run into any issues importing, refer to the official Microsoft documentation on importing solutions.

What’s Next

This Power Automate SharePoint file Teams alert introduced you to multi-app automation — one of the most widely used patterns in Power Automate. You connected SharePoint and Teams so that an action in one app automatically triggers a notification in the other.

In Flow 4, you will build something that makes a real difference to team culture: an automatic welcome message that greets every new member the moment they join your Microsoft Teams team. No more awkward silences when someone new joins — your flow handles the introduction.

Continue with Flow 4 in the Power Automate Beginner Series →