Feature coming soon
This feature is not available in the current beta. The guide below describes the intended experience once it is released.
Use an external workflow when a ChangePilot item needs an owner, due date, approval or completion record. A shared label can identify items for that workflow, while Planner or your ITSM platform manages the resulting work.
Agree the handoff
Choose the organisation, source and selection rule. For example, use an organisation label such as Create service review for items that the review team wants in its work queue. Agree who applies the label and who owns triage in the destination.
Build the flow
Design an authorised API-based connection for your external flow. This guide does not establish that a packaged ChangePilot Power Automate connector is available.
Use a scheduled flow to retrieve new or updated items, or query the agreed label and filters.
For each result, look up a destination record using the ChangePilot source and stable item ID.
Create a task or ticket when no mapping exists. Include the title, source ID, ChangePilot link and the information your team needs for triage.
When a mapping exists, update the relevant announcement details without duplicating the task.
Save the mapping and retrieval progress only after the destination action succeeds.
Keep dates and ownership meaningful
A Microsoft rollout date is not automatically your team's task deadline. Set a preparation or review deadline that reflects the work required. Preserve the original Microsoft date as context and read the announcement before deciding an action.
Choose an explicit destination owner or triage queue. A ChangePilot impact rating does not assign responsibility, and adding a label alone does not create a task.
Test the full lifecycle
Test a new item, an updated item, a retry after a destination failure, and an item that already has a completed task. Confirm that retries do not create duplicates and that source updates do not unexpectedly reopen completed work.
The intended integration is an external API-based pull workflow. The supported saved-View and Label retrieval contract must be confirmed before you build against it. The SaaS product is not a native workflow engine. Enterprise (ChangePilot On-Tenant) is a separate option for a Dataverse-based operational workflow; use its own product guidance for that experience.