**Alert Relay Documentation**

Guidance for building Alert Relay flows, choosing the right action, and understanding SharePoint version-history comparisons.

# Get Detailed Item Alert HTML

`Get Detailed Item Alert HTML` generates an email body showing what changed in a SharePoint item.

Use this action when you want Alert Relay to prepare the email content for you instead of building the email body manually in Power Automate.

## When to use this action

- you want to send an alert email after a SharePoint item is created or modified
- you want the email to show previous and current values where available
- you want Alert Relay to generate the email body and suggested subject for you

## Typical flow shape

This action is commonly used in a flow like this:

1. SharePoint trigger: `When an item is created or modified`
2. Alert Relay action: `Get Detailed Item Alert HTML`
3. Email action such as `Send an email (V2)`

## Inputs

- **Site URL** (`siteUrl`): string. The SharePoint site that contains the list or library.
- **List or Library** (`listId`): string. The SharePoint list or library that contains the item. You can select it from the dropdown, enter the exact list title, or enter the list GUID.
- **Item ID** (`itemId`): integer. The SharePoint item `ID`, usually from the trigger.
- **Compare From** (`triggerWindowStartToken`): string. For most trigger-based flows, use `TriggerWindowStartToken`. If left blank, Alert Relay compares the current item against the first version in the item's version history.
- **Include Minor Versions** (`includeMinorVersions`): boolean. Includes draft or minor versions in the comparison instead of using major versions only. Defaults to `false`.
- **Include Unchanged Fields** (`includeUnchangedFields`): boolean. Includes unchanged fields in the generated output as well as changed fields. Defaults to `true`.
- **Date Format** (`dateFormat`): string. Controls how dates are displayed in the output. Defaults to `yyyy-MM-dd`.
- **Time Format** (`timeFormat`): string. Controls how times are displayed in the output. Defaults to `HH:mm:ss`.
- **Timezone** (`timezone`): string. Controls which timezone Alert Relay uses when displaying date and time values. Defaults to `UTC`.

## Outputs

### **HTML Body** (`htmlBody`)

The generated HTML body for the email.
Type: string.

### **Suggested Subject** (`subject`)

A suggested subject line for the email.
Type: string.

### **Item Title** (`itemTitle`)

The SharePoint item title or file name.
Type: string.

### **Item URL** (`itemUrl`)

A link back to the SharePoint item.
Type: string.

### **Is New Item** (`isNewItem`)

Indicates whether the result should be treated as a new-item style alert.
Type: boolean.

### **Success** (`success`)

`true` if the action completed successfully.
Type: boolean.

### **Message** (`message`)

A human-readable message describing the result.
Type: string.

### **Error** (`error`)

Error details when the action fails.
Type: string.

## How to use the outputs

In your email action, use:

- `Subject` -> Alert Relay **Suggested Subject** (`subject`)
- `Body` -> Alert Relay **HTML Body** (`htmlBody`)

Make sure the email action treats the body as HTML.

## What the generated email is for

This action is designed for alert-style emails that help the recipient quickly see:

- which item changed
- who changed it
- when it changed
- which fields changed
- the previous and current values, where available

## Example scenarios

- send a notification when a list item moves from `Draft` to `Approved`
- send an alert when an assigned person changes on a task or request item
- send a readable update when a document library file is changed and recipients need the before-and-after values

## When to use a different action

Use [Use Detailed JSON Changes](/content/alert-relay/docs/use-detailed-json-changes/index.html) instead when:

- you want to inspect each changed field in flow logic
- you want to branch or filter based on specific fields
- you want to build your own custom output

Use [Parse Compare From](/content/alert-relay/docs/parse-compare-from/index.html) when:

- you need to inspect or make decisions based on the trigger token itself