# Power Automate: Email Yourself When a SharePoint List Item Is Added

> Build a flow that sends an email when a SharePoint list item is created or changed, add a condition, and fix the common trigger and licensing problems.

Source: https://www.epifive.com/blog/power-automate-email-new-sharepoint-list-item · Published 2026-11-19 · EpiFive

## Key takeaways

- The SharePoint trigger When an item is created starts a flow for each new list item, and When an item is created or modified also fires on every edit.
- The quickest start is the list's Integrate > Power Automate > Create a flow menu and the template that sends a customized email for a new item.
- Add a Condition after the trigger to email only for the items you care about, with Send an email (V2) under If yes.
- Flows for lists work only in generic lists and libraries, not custom list templates such as Announcements, Contacts, Events or Tasks.
- Check the flow's run history first when nothing arrives, then connections, list type and whether the flow was turned off.

To get an email when someone adds an item to a SharePoint list, create a cloud flow in Power Automate that uses the SharePoint trigger **When an item is created** and follows it with the Outlook action **Send an email (V2)**. The fastest route is the template that appears under **Integrate** > **Power Automate** > **Create a flow** on the list itself. Use **When an item is created or modified** instead if you also want a message each time a row is edited.

This guide walks through the template route, the same flow built from scratch, adding a condition so only some items trigger a message, testing, and fixing the usual reasons a flow stays silent.

## Who this is for and what you will have

This is for anyone who manages a SharePoint list in Microsoft 365, such as a request tracker or issue log. You do not need to write code. By the end you will have a flow that starts when a list item is created, emails values from that item, optionally sends only when a column matches your rule, and has been tested.

To replace the classic SharePoint "alert me" feature, see [Replacing SharePoint alerts with Rules and Power Automate after retirement](https://www.epifive.com/blog/sharepoint-alerts-replacement-rules-power-automate). This article is the single-flow tutorial.

## Prerequisites

Before you start, confirm the following:

- A Microsoft 365 account that can edit the list (you need permission to create flows from it) and a mailbox in Exchange Online, because the email action sends through the Outlook connector.
- A **generic** SharePoint list. Microsoft's SharePoint connector reference states that flows for lists are supported only in generic lists and generic document libraries, and that custom list and library templates are currently unsupported, including Announcements, Contacts, Events and Tasks lists.
- The site address of the list, for example `https://contoso.sharepoint.com/sites/sales`, and the exact list name.
- A rough idea of who should receive the email. A shared mailbox or a distribution address works better than a single person who may leave.

About licensing: the connector reference lists the SharePoint connector as **Standard** class for Power Automate. The email action comes from the Office 365 Outlook connector. Your plan's own terms still decide what you can run, so read [Power Automate licensing and premium connectors explained](https://www.epifive.com/blog/power-automate-licensing-premium-connectors) if you are unsure.

## Choose the right trigger

The SharePoint connector has several list triggers that sound alike. These three matter for this task, with the descriptions Microsoft gives in the connector reference:

| Trigger | When it fires | Use it when |
| --- | --- | --- |
| When an item is created | Triggers when an item is created. | You only want to hear about new rows. |
| When an item is created or modified | Triggers when an item is created, and also each time it is modified. | You want a message for new rows and for every edit. |
| When an item or a file is modified | Triggers when an item is modified, but not when it is created. | You only care about changes to existing rows. |

All three take the required parameters **Site Address** and **List Name**. The first two also offer an optional **Limit Columns by View** parameter, described as a way to avoid column threshold issues by only using columns defined in a view. On a large list with many lookup columns, point it at a view that contains only the columns the flow needs.

## Method 1: build it from the list template

This is the route Microsoft documents in its tutorial "Send an email when a new item is created or modified in a SharePoint list". The tutorial uses a **Projects** list, and your list name will differ.

1. Open the SharePoint site and browse to your list.
2. On the list's command bar, select **Integrate** > **Power Automate**. The menu expands to show **Create a flow**, **See your flows** and **Configure flows**.
3. Select **Create a flow**. A **Create a flow** panel lists templates for the list.
4. Select the template that reads "Send a customized email when a new SharePoint list item is added." A new browser tab opens on the Power Automate site showing the template name, its description and the connections it uses.
5. Check the connection information. In the dropdowns, confirm **SharePoint Site Address** and **SharePoint List Name** are correct. A green check mark means the connection to the service succeeded with your credentials.
6. Select **Create Flow**. Power Automate tries to establish the connections, then shows the flow details page. The flow is now active and runs whenever new items are added to the list.
7. Select **Edit** on the top command bar to open the flow designer.
8. Select the **When the new item is created** trigger to see the site address and list name it was given.
9. In the **Send Email** action, select **Edit**. Microsoft's tutorial notes the inputs are filled with dynamic values from the **Get my profile** and **When the new item is created** actions. Hover over a dynamic value to see which property it reads. For example, **Email** reads the **Mail** property from **Get my profile**.
10. Select **Save**.

The template sends the message to the person who created the flow, because that address comes from **Get my profile**. If a team should be notified, replace the **To** value with a fixed address, as shown below.

### Edit the message body

To add information to the email, as in the tutorial:

1. In the flow designer, select **Edit**, then select the **Send Email** action.
2. In the **Body** input, type the label text you want, for example `Owner:`.
3. With the cursor still in **Body**, use the **dynamic content** list that appears beside the action. Search for the column name.
4. Select the value. For a **person** column such as Owner, Microsoft's tutorial shows that SharePoint passes the person details as separate properties, such as **Owner DisplayName**, email, job title and picture, so you choose the property you want.
5. Select **Save**.

Dynamic values come from the trigger's output, which Microsoft describes as dynamic: the columns of your list appear as selectable fields.

## Method 2: build the flow from scratch

You may prefer a blank flow, especially if you want a shared mailbox as the sender or a particular subject line. The pieces are the same as in the template.

1. Sign in to Power Automate at `https://make.powerautomate.com` or `https://make.microsoft.com` and create an automated cloud flow.
2. Add the trigger **When an item is created** from the SharePoint connector.
3. Set **Site Address** by selecting your site in the dropdown, and set **List Name** by selecting the list in the dropdown.
4. Add a new step, search for **Send an email (V2)** and select it.
5. Fill in **To**, **Subject** and **Body**. Click inside each box and use the dynamic content list to insert the list's **Title**, **Created By** or other columns.
6. Name the flow something specific, such as "Notify sales team: new request", and save it.

Two details are worth knowing. First, Microsoft's SharePoint reference warns that if you use the list name as a dynamic value in **List Name** and the name contains a period, for example `MySharePoint.List`, the flow errors. Select the list from the dropdown, or enter the list's ID instead. Second, if you want mail to come from a shared mailbox, the Outlook connector has a separate action, **Send an email from a shared mailbox (V2)**. Its description says your account should have permission to access the mailbox, and the connector page adds that it is expected to work for the Microsoft 365 shared mailbox feature only and not for shared mailboxes converted from personal mailboxes.

## Add a condition so only some items send mail

An email for every new row becomes noise quickly. A condition limits it to items that match a rule, such as a priority of High. Microsoft's "Add a condition to a cloud flow" page describes the procedure, using different example fields. Applied to your list:

1. Open the flow and select **Edit**.
2. Under the trigger, select **New step** > **Condition**.
3. On the **Condition** card, select the empty box on the left. The **Dynamic content** list opens. Choose your column, for example **Priority Value** for a choice column.
4. In the middle box, choose the operator, such as **is equal to** or **is greater than or equal to**.
5. In the box on the right, type the value, for example `High`.
6. Move the **Send an email (V2)** action into the **If yes** branch, or select **Add an action** on the **If yes** side and add it there.
7. Optionally add an action on the **If no** side if you want something to happen for the other items.
8. Select **Save**.

Microsoft's page adds that you can build complex conditions with the **Add** button on the condition card. Use it when you need more than one test, such as priority High and category Security.

## Test the flow

Microsoft's tutorial gives two ways to test, and both work with your own list.

**Test from the designer:**

1. In the flow designer, select **Test** on the top command bar.
2. In the **Test Flow** panel, select **I'll perform the trigger action**, then select **Save & Test**. A message tells you to add a new list item.
3. Keep the flow designer tab open. Open the list in another tab, select **New**, fill in the columns and select **Save**.
4. Return to the designer tab. The run appears, and a green check mark beside each action means it succeeded.
5. Select an action to see its inputs and outputs, which shows the actual values that replaced the dynamic content.

You can also add an item to the list and wait for the email. If your condition filters items, test one that should match and one that should not.

## Troubleshooting

Start every investigation on the flow's details page, where run history shows whether the flow ran, which action failed and what it received.

### The flow never starts

- **Wrong list type.** The SharePoint reference says flows for lists are supported only in generic lists and generic document libraries. Announcements, Contacts, Events and Tasks lists are named as unsupported.
- **Wrong trigger.** When an item or a file is modified does not fire on creation. Use created, or created or modified.
- **Name with a period.** A dynamic List Name containing a period causes an error. Choose the list from the dropdown or use its ID.
- **Flow turned off.** Microsoft's limits page says a cloud flow whose trigger or actions fail continuously is turned off after 14 days, and a flow that is not triggered within 90 days might be turned off. It also says flows owned by users with premium licenses, or assigned capacity licenses, are not subject to the inactivity suspension, and owners are notified 30 days before suspension.

### The flow runs but no email arrives

- Open the run and look at **Send an email (V2)**. A green check mark means Outlook accepted the message, so check the junk folder and any mail-flow rules.
- Confirm the **To** address. The template defaults to the profile of the person who created the flow.
- Outlook connector limits: the connector page lists a maximum mail content length of 49 MB and a throttle of 300 API calls per connection per 60 seconds. It also states each email counts as one API call per connection even with several recipients. A burst of hundreds of list items can hit the throttle, so batch the notifications into a daily summary if your list receives that many items.

### Access and sign-in problems

- The connector reference notes conditional access policies, such as multifactor authentication or device compliance policies, might block access to data through the connector.
- It also notes guest user accounts cannot view or retrieve drop-down list information in connector operations. If a guest builds the flow, the dropdowns for site and list can appear empty.

### Dynamic content looks wrong

- A person column returns an object with properties. Choose the property you want, such as **Owner DisplayName**, rather than pasting the whole object.
- Term set label updates do not automatically appear in a connected flow. Microsoft's workaround is to edit the affected list item directly to force a refresh.

## Maintenance checklist

Use this checklist when the flow goes live:

- The flow lives under a shared or service account, or has a co-owner, so it survives a staff change.
- The **To** address is a group or shared mailbox.
- The trigger matches the intent: created only, or created and modified.
- The run history is checked after the first few real items.
- Someone knows the flow can be switched off after repeated failures or long inactivity, and that owners are warned beforehand.

For flows that notify people about problems in other flows, [Power Automate error handling with try-catch scopes](https://www.epifive.com/blog/power-automate-error-handling-try-catch) shows how to add a failure notification to this pattern.

## What we checked

- Opened the Microsoft Learn tutorial "Send an email when a new item is created or modified in a SharePoint list" on 2026-11-19 (page metadata updated 2022-06-29). The template steps, panel labels, **Test Flow** panel wording and the **Owner DisplayName** edit are taken from it. The page is older, so the labels may have shifted slightly in the current interface.
- Opened the SharePoint connector reference on learn.microsoft.com on 2026-11-19 (page metadata updated 2026-08-01). The trigger descriptions, the **Site Address**, **List Name** and **Limit Columns by View** parameters, the Standard class for Power Automate, the generic-list limitation and the period-in-name error come from it.
- Opened "Add a condition to a cloud flow in Power Automate" on 2026-11-19 (metadata updated 2026-10-29). The **New step** > **Condition**, the operator box, **If yes** and **If no** labels and the **Add** button for complex conditions are quoted from it. Its example uses other fields, so the Priority column in this article is our own illustration.
- Opened "Limits of automated, scheduled, and instant flows" on 2026-11-19 (updated 2026-11-11) and confirmed the 14-day and 90-day turn-off rules and the 30-day owner notice quoted above.
- Opened the Office 365 Outlook connector page on 2026-11-19 (updated 2026-10-01) and confirmed the 49 MB mail content limit, the 300 calls per 60 seconds throttle and the shared mailbox action notes. We read only the first part of that page and did not verify the parameter tables for the email actions, so field names such as To, Subject and Body follow Microsoft's tutorial and designer usage.
- There is no command output to quote, because the flow is built in a browser. We did not take or add screenshots.
- Not tested on a live tenant or with a real list; steps follow Microsoft's documentation as of 2026-11-19.

Last tested: 2026-11-19

## References

- [Send an email when a new item is created or modified in a SharePoint list (Microsoft Learn)](https://learn.microsoft.com/en-us/sharepoint/dev/business-apps/power-automate/get-started/create-your-first-flow)
- [SharePoint connector reference (Microsoft Learn)](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
- [Office 365 Outlook connector reference (Microsoft Learn)](https://learn.microsoft.com/en-us/connectors/office365/)
- [Add a condition to a cloud flow in Power Automate (Microsoft Learn)](https://learn.microsoft.com/en-us/power-automate/add-condition)
- [Limits of automated, scheduled, and instant flows (Microsoft Learn)](https://learn.microsoft.com/en-us/power-automate/limits-and-config)

## Frequently asked questions

### Which trigger should I use to send an email when a SharePoint list item is added?

Use the SharePoint trigger When an item is created. Microsoft's connector reference describes it as firing when an item is created. If you also want to be told about edits, use When an item is created or modified, which fires when an item is created and each time it is modified.

### Do I need a Power Automate premium license to email on a new SharePoint item?

Microsoft's connector reference lists the SharePoint connector as Standard class in Power Automate, and the Send an email (V2) action belongs to the Office 365 Outlook connector. Check the licensing page for your plan, but the SharePoint trigger itself is not a premium connector.

### Why does my SharePoint flow not start for a new item?

Common causes are a list built from a custom template such as Announcements, Contacts, Events or Tasks (flows for lists are supported only in generic lists and libraries), a dynamic List Name that contains a period, or a flow that was turned off after repeated failures. Pick the list from the dropdown and check the run history first.

### Can a flow email me only when a column has a certain value?

Yes. Add a Condition after the trigger, pick the column from the dynamic content list, choose an operator such as is equal to, and put the Send an email (V2) action under If yes.

