✱ How to use ChangePilot flow templates
Import an optional flow template, keep its components in Configuration and verify the result before use.
Applies to: optional customer automation for the Dataverse-based Enterprise App. These templates require an administrator or maker familiar with Power Automate and the relevant connections.
Templates are supplied as unmanaged solutions. Keep customer components in Configuration. Unmanaged customisations can affect the active behaviour of managed components; they are not an isolated runtime. See solution layers.
Import and organise the template
- Choose the template below and download its ZIP from the linked article. Confirm the target ChangePilot environment in Power Apps.
- Open Solutions and import the template ZIP as instructed for that template. Check the incoming solution’s identity and that it is unmanaged.
- Open the imported solution and record all its components, including flows, connection references and any new choices or variables.
- Open the existing customer Configuration solution. Use Add existing to include the template’s required components. Components already included do not need a duplicate.
- Confirm that every required component is visible in Configuration. Configure connections and flow conditions using the template article and your organisation’s approved identities.
Before removing the temporary solution container
Only consider deleting the imported unmanaged template solution container after confirming its components are present in Configuration. Do not delete the managed ChangePilot solution, Configuration, or individual components. If the solution type or identity is unclear, leave it in place and ask your administrator to check.
Deleting an unmanaged solution container leaves its components in the environment; uninstalling a managed solution can remove components and data. See Microsoft’s solution concepts.
Configure and validate
Open the flow from Configuration, apply the template-specific settings, save and publish where required. Check connection references, intended triggers and recipients. Agree a controlled test because a run may send real messages. Verify the destination and duplicate behaviour before wider use.
Available templates
- Template 001: send an item to another team or business unit when a configured tag is first added.
- Template 002: notify an individual when a new ChangePilot action is created.
For help, contact support@changepilot.cloud or your ChangePilot contact to confirm the assistance available under your agreement.
Documentation reviewed: 12 November 2026.