Extend a pipeline with a cloud flow

Based on the configuration of a pipeline stage, you can take different actions during the life of a pipeline deployment. The system activates optional gates when you need the deployment to pause. These gates await a status update before proceeding to the next step or stopping the deployment.

To extend a pipeline with a cloud flow, you can add triggers or actions that provide another level of interaction.

Triggers

For cloud flows that react to a business event, you can configure the When an action is performed Dataverse trigger for that event. To do so, you can use a trigger condition that limits the scope of the flow to only the applicable cases that you create the flow for.

Expressions in the trigger conditions can help limit the scope of when a pipeline deployment triggers a flow, such as:

• For a specific pipeline name:

  @equals(triggerOutputs()?['body/OutputParameters/DeploymentPipelineName'], 'Extend a Pipeline Demo')

• For all pipelines that contain a specific stage name:

  @contains(triggerOutputs()?['body/OutputParameters/DeploymentStageName'], 'Move to QA')

Actions

If you configure the pipeline with gates, then in most cases, after the flow logic completes, the cloud flow should use Perform an unbound action from Dataverse to stop the deployment or let it continue. The status parameter values of the action are as follows:

• 10 - System generated (pending)

• 20 - If the deployment can continue (success)

• 30 - If the deployment should stop (fail)

You can take advantage of all capabilities of Power Automate cloud flows to extend a pipeline. These capabilities include options to read or update records by connecting to different data sources, to send emails or approvals, and more.

Next steps

Now you learned how to extend a pipeline with a Power Automate cloud flow. Next, you apply these concepts to add an approval stage to a pipeline.