What a configuration could hand over
In a company running on Microsoft 365, not every step needs a connection of its own. The configurator can call a flow that carries on into Outlook, Teams, SharePoint or Dynamics 365 as your process requires. You can then edit those flows yourselves, without touching the configurator.
HTTP trigger
The configurator could call the “When an HTTP request is received” trigger, and the flow would receive the configuration as JSON matching the schema you set in the trigger.
Microsoft 365 actions
The flow can write the enquiry to a SharePoint list or an Excel table, email it through Outlook or post it in Teams.
Dataverse and Dynamics 365
In a company on Dynamics 365, the flow can turn the configuration into a lead or an opportunity in Dataverse.
Approvals
For non-standard dimensions or a higher price, the flow can first start an approval and release the enquiry only once a manager agrees.
What we need to connect it
Someone on your side creates the flow in a suitable Power Automate environment; we supply the JSON schema and sample configurations.
The trigger lets you choose who may call it: specific users in your tenant, any user in the tenant, or the legacy Anyone option with no further authentication; the first two would need the configurator to present a Microsoft Entra ID token.
We check licensing first: Microsoft 365 licences cover standard connectors only, while premium ones need Power Automate Premium or another licence that includes them.
Until the live version is signed off, testing runs on a separate flow or in a test environment.
Worth deciding up front
- The trigger URL contains a SAS signature; if it is regenerated, for instance after the URL leaks, the new URL has to be set in the configurator as well.
- Flows have daily action limits by licence and return a 429 error when connector limits are exceeded, which is worth weighing for larger flows.
- Access to customer contact details in SharePoint or Excel follows your Microsoft 365 permissions, not the configurator.
Questions about this connection
Is a Microsoft 365 licence enough without Power Automate Premium?
For flows that use standard connectors only, Microsoft 365 licences are enough. Which connectors your flow will use, the trigger included, and whether any of them is premium is something we would check with your administrator before setup.
Can we edit the flow later without you?
The flow lives in your tenant and you edit it yourselves in Power Automate. The configurator only needs the trigger URL and JSON schema to stay the same, or a heads-up from you before they change.
Other integrations
Put Power Automate to work in your sales.
Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.