Integration Details

Power Automate

Route every submission into Teams, Outlook, SharePoint, Dataverse, SQL and anything else Power Automate connects to.

Talk to us

Overview

This is the integration that opens the most doors, and it works by composition rather than by a dedicated connector.

Monival dispatches an HTTP POST webhook when a form receives a submission. Power Automate’s When an HTTP request is received trigger accepts that POST and starts a flow. From that point every action in Power Automate’s connector library is available to you — Microsoft Teams, Outlook, SharePoint, OneDrive, Dataverse, SQL Server, Excel Online, Dynamics 365, Planner, Approvals, and several hundred third-party services.

Be clear about what this is. There is no certified Monival connector in the Power Automate connector gallery. You are not selecting Monival from a list. You are pointing a Monival webhook at a Power Automate HTTP trigger URL, and Power Automate does the rest. That is a genuinely powerful pattern and it is also a plain one, and we would rather describe it accurately than let you discover the difference during a trial.

How it works

  1. Create a flow in Power Automate using the When an HTTP request is received trigger.
  2. Copy the generated HTTP POST URL from the trigger. It contains a signature in the query string, which is what authenticates the call.
  3. Paste it into your Monival form’s webhook URL setting. The setting is per form, so different forms can drive different flows.
  4. Add actions to the flow. Parse the JSON body, then route, notify, store or transform it however the process requires.

The payload

Monival posts a JSON body containing:

  • event — currently submission.created
  • formId — the form the submission belongs to
  • submissionId — the submission’s identifier
  • organizationId — your organisation
  • submittedAt — the submission timestamp
  • syncSource — where it came from (web, mobile, offline queue)
  • answers — the submitted answers, keyed by question

Use Power Automate’s Parse JSON action with a schema generated from a sample payload so that downstream actions get typed fields rather than raw text.

What people build with it

  • Alert a Teams channel when a submission arrives from a priority site, or when a numeric answer crosses a threshold.
  • Email a programme manager the moment a protection or safeguarding form is submitted.
  • Append rows to a SharePoint list or Excel Online workbook that a team already works from.
  • Write to Dataverse or SQL Server to join Monival data with other organisational data.
  • Start a Power Automate approval for submissions that need a decision outside Monival’s own approval workflow.
  • Create a Planner task when a submission records an issue requiring follow-up.

Delivery behaviour — read this before you design a flow

The webhook is fire-and-forget, and that has design consequences:

  • Delivery is attempted once. There is no retry queue.
  • The request times out after 5 seconds. A flow that is slow to acknowledge may not be reached.
  • Failures are logged on the Monival side and not surfaced as a submission error — the submission is still saved. Your data is never at risk from a webhook failure, but a notification can be missed.
  • The payload is not HMAC-signed. The Power Automate trigger URL’s own signature is what keeps the endpoint from being trivially callable, so treat that URL as a secret.

The practical implication: use this for notification, routing and convenience automation, and do not make it the only path by which data reaches a system of record. Where a Power Automate flow must never miss a submission, pair it with a scheduled flow that pulls from the Power BI / Excel data feed and reconciles.

Where this goes further

Sibasi builds on Microsoft Power Platform as a core delivery practice, with live client implementations. Where an organisation needs more than event routing — model-driven apps, Dataverse as a results substrate, or integration with Dynamics 365 Business Central — that is delivered as an implemented solution, scoped as a project rather than enabled as a setting.