MCNE Notification (Preview)

Send multi-channel notifications from your MCNE templates.

This connector is available in the following products and regions:

MCNE Notification

MCNE (Multi-Channel Notification Engine) is a multi-tenant notification platform by EXE Software SRL. This connector lets you send templated, multi-channel notifications — email, Microsoft Teams, SMS, and WhatsApp — directly from your flows, using the message templates and delivery providers you have already configured in MCNE.

Your notification content lives in MCNE as reusable templates. The connector reads those templates, renders each one's variables as individual input fields in the designer, and sends the result through the delivery channels configured for that template.

Publisher

EXE Software SRL — https://mcne.live/

Prerequisites

1. An active MCNE subscription. Purchase an MCNE plan on the Azure Marketplace. During provisioning, your Microsoft Entra tenant is linked to your MCNE account automatically.
2. Tenant administrator consent. The connector requests the delegated permissions Notifications.Send and Templates.Read. A tenant administrator approves these once.
3. At least one template enabled for connector use. In the MCNE portal (/templates), switch on the Connector toggle for each template you want available here. This is opt-in: templates are hidden from the connector until you enable them.
4. Delivery providers configured in MCNE. Your own SMS/email providers (for example Twilio or SendGrid) are configured per channel in the MCNE portal.

How to get credentials

No API keys or secrets are needed. The connector uses Microsoft Entra ID sign-in:

1. Add an MCNE action to a flow and choose Sign in.
2. Sign in with your organization's work account and accept the consent prompt. If consent requires an administrator, your tenant admin approves it once for the whole organization.
3. The resulting connection is reused by every flow in your environment.

Your Entra tenant is matched to your MCNE account, so you only ever see your own templates.

Get started with your connector

1. Add the Send from template action to a flow.
2. Pick a template from the Template dropdown — it lists the templates you enabled for connector use.
3. The template's variables appear as individual fields. Bind trigger or Dataverse values to each one.
4. Fill in at least one Recipient address (email, Teams, SMS, or WhatsApp).
5. Run the flow. The action returns the notification id and a queued status.

Example

A flow triggered by a new high-priority Dataverse case selects the case_acknowledgement template, binds the case number and owner name to the template variables, and sends an email and SMS to the assigned agent.

Supported operations

Send from template

Sends a notification built from one of your MCNE templates. Inputs: the template, the recipient's delivery addresses, and a value for each template variable. Optional inputs let you restrict the template to a specific MCNE application or supply your own notification id.

Known issues and limitations

• Templates are opt-in. Only templates with the Connector toggle enabled in the MCNE portal appear in the picker. If a template is later disabled, flows referencing it fail with a clear "not enabled for the external connector" error.
• Delivery is asynchronous. A successful response means the notification was accepted and queued, not that it was delivered. Per-channel delivery status is tracked in MCNE.
• One recipient per call. Each action call targets a single recipient, which may have several channel addresses. Use a loop to notify multiple recipients.
• Channels follow the template. The notification is sent on the channels enabled for the chosen template. Supplying an address for a channel the template does not use has no effect, and an enabled channel with no address is not attempted.
• Template variables are text. All variable inputs are strings; format dates and numbers before binding them.
• Usage is metered. Notifications sent through the connector count towards your MCNE plan.
• Premium licensing. As a connector to an external service, this is a premium connector and requires appropriate Power Automate licensing.

Common errors and remedies

Support

• Email: mcne@exesoftware.ro
• Website: https://mcne.live/
• Privacy policy: https://mcne.live/privacy-policy/

Creating a connection

The connector supports the following authentication types:

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.

Actions

Send from template

Definitions

SendFromTemplateResponse