Alert Relay (Preview)

Alert Relay helps replace retiring SharePoint Alerts with richer, modern notifications. It returns detailed field-level changes as well as ready-to-use alert HTML, so you can show exactly what changed instead of generic modified notifications. You can also use change and version information in flow decisions and conditions.

This connector is available in the following products and regions:

Service Class Regions
Copilot Studio Premium All Power Automate regions except the following:
     -   US Government (GCC)
     -   US Government (GCC High)
     -   China Cloud operated by 21Vianet
     -   US Department of Defense (DoD)
Logic Apps Standard All Logic Apps regions except the following:
     -   Azure Government regions
     -   Azure China regions
     -   US Department of Defense (DoD)
Power Apps Premium All Power Apps regions except the following:
     -   US Government (GCC)
     -   US Government (GCC High)
     -   China Cloud operated by 21Vianet
     -   US Department of Defense (DoD)
Power Automate Premium All Power Automate regions except the following:
     -   US Government (GCC)
     -   US Government (GCC High)
     -   China Cloud operated by 21Vianet
     -   US Department of Defense (DoD)
Contact
Name independNET Support
URL https://independnet.com.au/alert-relay/support
Email support@alertbridge.com.au
Connector Metadata
Publisher independNET Software
Website https://independnet.com.au/alert-relay/
Privacy policy https://independnet.com.au/alert-relay/privacy
Categories Collaboration;Productivity

Alert Relay

Alert Relay for Power Platform and Microsoft 365 Copilot

Alert Relay helps organisations replace classic SharePoint Alerts with modern Power Automate and Copilot Studio solutions. It compares SharePoint items, files and pages against earlier versions and returns structured change information, version history and ready-to-use notification content without requiring makers to build complex SharePoint version comparison logic.

Overview

SharePoint triggers can identify that an item, file or page has changed, but they do not provide a complete comparison of previous and current values.

Building that comparison often requires makers to retrieve versions, interpret change tokens, compare fields and format results for notifications or downstream processing.

Alert Relay centralises that work through reusable actions for Power Automate and Copilot Studio.

Key Features

Alert Relay centralises that work through reusable actions that can:

  • identify detailed field-level changes
  • return previous and current field values
  • generate ready-to-use HTML for SharePoint alert emails
  • retrieve item, file and page version history
  • compare from a trigger token, change token, version label or date
  • format supported complex SharePoint field types
  • return structured information for Power Automate and Microsoft 365 Copilot

Alert Relay supports SharePoint lists, document libraries and Site Pages libraries.

Getting Started

A typical SharePoint alert flow includes:

  1. A SharePoint trigger, such as When an item is created or modified.
  2. An Alert Relay action, such as Get Item or File Changes as Alert HTML.
  3. An email or another notification action that uses the returned subject and HTML body.

For conditions, custom formatting or Microsoft Copilot Studio agent scenarios, use Get Detailed Item or File Changes and work with the structured change information it returns.

For historical SharePoint versions, use Get Item or File Version History.

Documentation

Documentation, action reference information, examples and getting-started guidance are available at:

Alert Relay documentation

Video Tutorials

Step-by-step walkthroughs, examples and how-to videos are available on the Alert Relay YouTube channel:

Alert Relay on YouTube

Licensing and Trial

Alert Relay licensing is tenant-wide. A single trial or subscription applies across the Microsoft Entra tenant, and its usage units are shared by Alert Relay flows and users in that tenant.

The 90-day trial starts automatically when any Alert Relay action first runs in the tenant and includes 300 usage units shared across the trial. For current plans and further details, see Alert Relay pricing and licensing.

Actions

Get Detailed Item or File Changes

Returns detailed field-level changes between the current version of a SharePoint item, file or page and an earlier version.

The action returns structured information including previous and current values, formatted values and comparison metadata. Use it when a flow or Microsoft Copilot Studio agent needs to inspect, summarise or act on individual changes.

Get Item or File Changes as Alert HTML

Generates ready-to-use HTML showing what changed in a SharePoint item, file or page.

The action also returns a suggested email subject, item title and item link. Use it to create richer SharePoint alert emails without building complex HTML and version comparison expressions in every flow.

Get Item or File Version History

Returns bounded, pageable version history for a SharePoint item, file or page.

The action can return selected SharePoint fields and supports version, date and SharePoint trigger-token boundaries. Use it for historical review, audit, reporting, approval and version-aware workflow scenarios.

Parse SharePoint Version Information

Decodes SharePoint trigger-window and change-token information.

Use this action to retrieve the token timestamp, apply date or version-based decisions, and filter unwanted minor or draft version triggers before calling a detailed change action.

Typical Uses

Alert Relay can help you:

  • replace classic SharePoint Alerts with Power Automate flows
  • send formatted notifications showing exactly what changed
  • compare previous and current values for important business fields
  • track changes to document metadata and SharePoint pages
  • retrieve SharePoint item and file version history
  • build approval, review, governance and audit workflows
  • provide structured SharePoint change information to Microsoft 365 Copilot

Authentication and Access

Alert Relay uses Microsoft Entra ID delegated authentication.

SharePoint access is performed in the context of the signed-in user. Alert Relay does not grant users additional SharePoint permissions, so users must already have access to the relevant SharePoint site, list, library, item or file.

Requirements and Supported Scope

  • Alert Relay supports SharePoint Online. SharePoint Server on-premises is not supported.
  • Actions run when called by Power Automate or another supported client. For change notifications, use an appropriate SharePoint trigger to start the flow.
  • Comparisons using SharePoint trigger tokens are based on the SharePoint trigger window. The resulting baseline may differ from an item-specific version boundary.
  • Detailed formatting is available for supported SharePoint field types. See the Alert Relay documentation for the current field-type reference.

Support

Website: https://independnet.com.au/alert-relay/

Support: https://independnet.com.au/alert-relay/support

Email: support@alertrelay.com.au

Privacy policy: https://independnet.com.au/alert-relay/privacy

Creating a connection

The connector supports the following authentication types:

Default Parameters for creating connection. All regions Not shareable

Default

Applicable: All regions

Parameters for creating connection.

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Throttling Limits

Name Calls Renewal Period
API calls per connection 100 60 seconds

Actions

Get Detailed Item or File Changes

Retrieves detailed, formatted field-level changes for a SharePoint list item or file, comparing the current version with a previous version. Use this when you want rich change data, not just the built-in SharePoint true/false change indicators. Results may include an important Alert Relay trial, subscription, or usage notice for the user.

Get Item or File Changes as Alert HTML

Returns ready-to-use Alert Relay HTML for SharePoint item changes, designed primarily for alert emails but also usable anywhere that HTML is supported. Results may include an important Alert Relay trial, subscription, or usage notice for the user.

Get Item or File Version History

Returns up to the requested number of versions for a SharePoint list item or file, newest first. Each version includes version details, column values, formatted text values, and indicators showing which columns changed from the preceding available version. Select the site and list or library while configuring this action to make its columns available as dynamic content. Results may include an important Alert Relay trial, subscription, or usage notice for the user.

Parse SharePoint Version Information

Decodes a SharePoint Compare From token. When Version Number and Modified Date are also supplied, it determines whether the item or file is a new version. Use this non-billable action in flow conditions before calling Alert Relay billable actions.

Get Detailed Item or File Changes

Retrieves detailed, formatted field-level changes for a SharePoint list item or file, comparing the current version with a previous version. Use this when you want rich change data, not just the built-in SharePoint true/false change indicators. Results may include an important Alert Relay trial, subscription, or usage notice for the user.

Parameters

Name Key Required Type Description
Site URL
siteUrl True string

Select a SharePoint site or enter the site URL.

List or Library
listId True string

Select a list or library, or enter its title or GUID.

Item ID
itemId True integer

ID of the SharePoint item or file to analyze for changes.

Compare From
triggerWindowStartToken string

Starting point for the comparison. Use the SharePoint trigger's TriggerWindowStartToken when available. You can also enter a version label, raw change token, or baseline date/time. Date-only values use midnight in the selected timezone, or UTC if no timezone is selected. Leave blank to compare with the previous version.

Include Minor Versions
includeMinorVersions boolean

Whether to include minor or draft versions when comparing changes. Defaults to false, so only major versions are compared.

Include Unchanged Fields
includeUnchangedFields boolean

Whether unchanged fields should be included in the response. Defaults to true.

Date Format
dateFormat string

Format used for DateTime fields (for example, 'yyyy-MM-dd', 'dd/MM/yyyy', 'MM/dd/yyyy'). Defaults to 'yyyy-MM-dd'.

Time Format
timeFormat string

Format used for the time portion of DateTime fields (for example, HH:mm:ss, HH:mm, hh:mm tt). Defaults to HH:mm:ss.

Timezone
timezone string

Timezone used when formatting dates and times (for example, America/New_York, Europe/London, Australia/Sydney). Defaults to UTC.

Returns

Name Path Type Description
Success
success boolean

True when the action completed successfully; false when validation or processing failed.

Message
message string

User-facing message describing the result of the operation. Agents and copilots should show this message to the user when it contains trial, subscription, usage, warning, or version-processing information.

Display User Notice
shouldDisplayUserNotice boolean

Indicates whether Alert Relay returned an important trial, subscription, or usage notice for the user.

User Notice Code
userNoticeCode string

Stable machine-readable reason for the user notice.

User Notice Severity
userNoticeSeverity string

Presentation severity for the user notice: information, warning, or critical.

User Notice
userNotice string

Important information about the Alert Relay trial, subscription, or usage.

User Notice Call to Action
userNoticeCallToAction string

What the user can do next, including the Alert Relay website and support email.

Changed Fields
changedFields array of object

List of compared SharePoint fields, including each field's name, previous value, current value, and whether it changed.

Column Value Has Changed
changedFields.hasChanged boolean

True if this field's value changed between the previous and current version

Previous Column Value (Text)
changedFields.previousAsString string

Formatted previous value as a human-readable string

Field Internal Name
changedFields.internalName string

Internal SharePoint field name

Field Name
changedFields.displayName string

Friendly display name for the field

Previous Column Value (Detailed)
changedFields.previous

Raw previous value. This property is dynamic and can be a string, number, boolean, object, array, or null depending on the SharePoint field type.

Current Column Value (Text)
changedFields.currentAsString string

Formatted current value as a human-readable string

Current Column Value (Detailed)
changedFields.current

Raw current value. This property is dynamic and can be a string, number, boolean, object, array, or null depending on the SharePoint field type.

Has Comparison Baseline
hasComparisonBaseline boolean

True if a distinct baseline version was resolved for comparison against the current version.

Is Baseline First Version
isBaselineFirstVersion boolean

True if the resolved baseline version is the first version ever recorded for the item or file.

Is New Item
isNewItem boolean

True when the item or file should be treated as new for the resolved comparison window rather than as an update.

Current Version Label
currentVersionLabel string

Version label of the current version (for example, '2.0', '5.0')

Previous Version Label
previousVersionLabel string

Version label used for comparison (for example, '1.0', '4.0')

Item or File Name
itemTitle string

Title or filename of the changed item or file.

Item or File URL
itemUrl string

Direct link to the changed SharePoint item or file.

Modified Date
modifiedDate date-time

Date and time of the latest modification.

Modified By
modifiedBy string

Display name of the user who last modified the item

Error
error string

Error details if success is false

Get Item or File Changes as Alert HTML

Returns ready-to-use Alert Relay HTML for SharePoint item changes, designed primarily for alert emails but also usable anywhere that HTML is supported. Results may include an important Alert Relay trial, subscription, or usage notice for the user.

Parameters

Name Key Required Type Description
Site URL
siteUrl True string

Select a SharePoint site or enter the site URL.

List or Library
listId True string

Select a list or library, or enter its title or GUID.

Item ID
itemId True integer

ID of the SharePoint item or file to analyze for changes.

Compare From
triggerWindowStartToken string

Starting point for the comparison. Use the SharePoint trigger's TriggerWindowStartToken when available. You can also enter a version label, raw change token, or baseline date/time. Date-only values use midnight in the selected timezone, or UTC if no timezone is selected. Leave blank to compare with the previous version.

Include Minor Versions
includeMinorVersions boolean

Whether to include minor or draft versions when comparing changes. Defaults to false, so only major versions are compared.

Include Unchanged Fields
includeUnchangedFields boolean

Whether unchanged fields should be included in the generated HTML. Defaults to true.

Date Format
dateFormat string

Format used for DateTime fields (for example, 'yyyy-MM-dd', 'dd/MM/yyyy'). Defaults to 'yyyy-MM-dd'.

Time Format
timeFormat string

Format used for the time portion of DateTime fields (for example, HH:mm:ss, HH:mm, hh:mm tt). Defaults to HH:mm:ss.

Timezone
timezone string

Timezone used when formatting dates and times (for example, America/New_York, Europe/London, Australia/Sydney). Defaults to UTC.

Returns

Name Path Type Description
Success
success boolean

True when the action completed successfully; false when validation or processing failed.

Message
message string

User-facing message describing the result of the operation. Agents and copilots should show this message to the user when it contains trial, subscription, usage, warning, or version-processing information.

Display User Notice
shouldDisplayUserNotice boolean

Indicates whether Alert Relay returned an important trial, subscription, or usage notice for the user.

User Notice Code
userNoticeCode string

Stable machine-readable reason for the user notice.

User Notice Severity
userNoticeSeverity string

Presentation severity for the user notice: information, warning, or critical.

User Notice
userNotice string

Important information about the Alert Relay trial, subscription, or usage.

User Notice Call to Action
userNoticeCallToAction string

What the user can do next, including the Alert Relay website and support email.

HTML Body
htmlBody string

HTML body for the alert message, ready to use in email or anywhere HTML is supported.

Generated Alert Subject
subject string

Suggested subject line for the alert

Item or File Name
itemTitle string

Title or filename of the changed item or file.

Item or File URL
itemUrl string

Direct link to the changed SharePoint item or file.

Is New Item
isNewItem boolean

Determines whether the generated alert describes the item or file as added or changed.

Error
error string

Error details if success is false

Get Item or File Version History

Returns up to the requested number of versions for a SharePoint list item or file, newest first. Each version includes version details, column values, formatted text values, and indicators showing which columns changed from the preceding available version. Select the site and list or library while configuring this action to make its columns available as dynamic content. Results may include an important Alert Relay trial, subscription, or usage notice for the user.

Parameters

Name Key Required Type Description
Site URL
siteUrl True string

Select a SharePoint site or enter the site URL.

List or Library
listId True string

Select the list or library whose version columns should be available as dynamic content in the flow.

Item ID
itemId True integer

SharePoint list item ID. This can be supplied dynamically at runtime, for example from a SharePoint trigger or an earlier flow action.

Maximum Usage Units
maximumUsageUnits True integer

Required caller-selected limit on the usage units this call may consume. Defaults to 1. This is a billing guard, not a version-count limit; one usage unit can return multiple complete versions. Use Maximum Versions to limit the number of version rows.

Maximum Versions
maximumVersions integer

Maximum total number of complete version rows to return across all pages. Leave blank to continue until the selected range, available history, or usage-unit budget ends. Each response contains no more than 100 versions.

Fields to Return
fieldsToReturn array of string

SharePoint columns to include in each version. Add one column per item. Leave Fields to Return empty to return every supported column. Selecting fewer columns can reduce response size and usage-unit work.

Compare From
fromVersion string

Starting point for the version history range. Use the SharePoint trigger's TriggerWindowStartToken when available. You can also enter a version label, raw change token, or baseline date/time. Date-only values use midnight in the selected timezone, or UTC if no timezone is selected. Leave blank for no older boundary.

Compare To
toVersion string

Ending point for the version history range. Use the SharePoint trigger's TriggerWindowEndToken when available. You can also enter a version label, raw change token, or date/time. Date-only values use midnight in the selected timezone, or UTC if no timezone is selected. Leave blank for no newer boundary.

Paging Token
continuationToken string

Token used to retrieve the next page of version history, if one was returned by a previous call.

Include Minor Versions
includeMinorVersions boolean

Whether to include minor or draft versions when retrieving version history. Defaults to false, so only major versions are returned.

Date Format
dateFormat string

Format used for DateTime fields (for example, 'yyyy-MM-dd', 'dd/MM/yyyy', 'MM/dd/yyyy'). Defaults to 'yyyy-MM-dd'.

Time Format
timeFormat string

Format used for the time portion of DateTime fields (for example, HH:mm:ss, HH:mm, hh:mm tt). Defaults to HH:mm:ss.

Timezone
timezone string

Timezone used when formatting dates and times (for example, America/New_York, Europe/London, Australia/Sydney). Defaults to UTC.

Returns

The outputs of this operation are dynamic.

Parse SharePoint Version Information

Decodes a SharePoint Compare From token. When Version Number and Modified Date are also supplied, it determines whether the item or file is a new version. Use this non-billable action in flow conditions before calling Alert Relay billable actions.

Parameters

Name Key Required Type Description
Compare From
compareFrom True string

TriggerWindowStartToken or raw SharePoint change token to decode. Version labels and ISO date/date-time values are not supported by this action.

Version Number
versionNumber string

Version Number from the SharePoint trigger or action, such as 0.1, 1.0, or 1.5. Used to identify minor/draft versions.

Modified Date
modifiedDate date-time

Modified date from the SharePoint trigger or action. Used to detect whether the visible SharePoint version changed during the trigger window.

Include Minor Versions
includeMinorVersions boolean

Whether minor/draft version numbers should count as new versions. Defaults to false.

Timezone
timezone string

Optional timezone for local comparison values, such as 'America/New_York', 'Europe/London', or 'Australia/Sydney' (IANA timezone ID). If omitted, only the UTC value is returned.

Returns

Name Path Type Description
Success
success boolean

True when the version information was parsed successfully; false when validation or processing failed.

Message
message string

User-facing message describing the result of the operation. Agents and copilots should show this message to the user when it contains trial, subscription, usage, warning, or version-processing information.

Token Date Time UTC
tokenDateTimeUTC date-time

Date and time from the Compare From token, returned in UTC.

Token Date Time Local
tokenDateTimeLocal date-time

Date and time from the Compare From token, converted to the selected Timezone.

Decoded Token
decodedToken string

Raw SharePoint change token after decoding. If Compare From was already a raw token, this matches the supplied value.

Is Base64 Token
isBase64Token boolean

True when the incoming token was base64 encoded.

Sequence
sequence integer

SharePoint change sequence value embedded in the token.

List GUID
listGuid uuid

List or library GUID embedded in the token.

Token Version
tokenVersion integer

Token version number.

Token Type
tokenType integer

SharePoint token type number.

Is New Version Detected
isNewVersionDetected boolean

True when the supplied trigger/action metadata shows a new visible SharePoint version should be processed. False when the version should be skipped. Null when there is not enough metadata to determine.

Is Minor Version
isMinorVersion boolean

True when the supplied Version Number is a minor/draft version. Null when Version Number was not supplied.

Is First Minor Version
isFirstMinorVersion boolean

True when the supplied Version Number is the first minor/draft version, typically 0.1. Null when Version Number was not supplied.

Is First Major Version
isFirstMajorVersion boolean

True when the supplied Version Number is the first major/published version, typically 1.0. Null when Version Number was not supplied.

Modified Date UTC
modifiedDateUtc date-time

Supplied Modified Date normalized to UTC. Null when Modified Date was not supplied.

Modified Date Local
modifiedDateLocal date-time

Supplied Modified Date converted to the selected Timezone. Null when Modified Date or Timezone was not supplied.

Error
error string

Error details if success is false.