Add nodes

A workflow consists of nodes that you connect together. Each node performs one step. You add nodes from the palette on the left side of the workflow editor. Make sure all nodes are connected and form a logical flow.

Triggers

Every workflow starts with a trigger. The trigger determines when the workflow is started.

Manual trigger

Start the workflow with a single click using the Run button on the workflows page. Use this during development and testing, or for analyses you run on demand.

Scheduled trigger

Start the workflow automatically at a fixed time. Configure:

• Frequency — Daily, weekly (choose desired days), or monthly (choose day of month).
• Time — The time at which the workflow starts.
• Timezone — Default: Europe/Amsterdam.

Data

DAX Query

Executes a DAX query against a Power BI dataset and passes the result to subsequent nodes.

• Choose the dataset.
• Write the DAX query yourself or let the AI generate one from a plain-language question.
• Set the maximum number of rows (default 1,000).
• Test the DAX query to verify it returns the desired data.

AI

AI Analysis

Analyzes data with AI based on a prompt you write.

• Write the prompt with the instruction for the AI.
• Include data from a previous node in the prompt via a variable (e.g. {{daxquery1.output}}).
• Optionally add relevant custom skills for additional analysis context.
• The result is available for subsequent nodes via this node's alias.

AI Review

Has the AI review and iteratively improve the output of a previous node.

• Select the source data from the previous DAX query.
• Select the output to review from the previous AI Analysis node.
• Write the review criteria in the prompt.
• Set the maximum number of iterations (default 3). The node stops earlier if the AI indicates the output meets the criteria.

Agents

AI Agent

An autonomous agent that independently designs, executes, and analyzes DAX queries.

• Choose the dataset the agent may query.
• Write an instruction in plain language — the agent determines which queries are needed.
• Set the maximum number of tool calls (1–20, default 10).
• Enable Extended thinking for more extensive reasoning on complex analyses (uses more tokens).

Logic

Condition

Splits the workflow into two paths based on a condition: true or false.

The condition can work in two ways:

• Based on a DAX Query node — compare a column value from the query result against a fixed value. E.g. if Revenue is greater than 100,000.
• Based on another node — compare the execution status of a node. E.g. if the AI Review node has status "Approved".

Configure the condition:

• DAX Query node: choose the source node, select a calculation, a column, and an operator (=, ≠, >, <, between, in, contains, starts with, ends with), and compare with a fixed value.
• Other node: choose the source node and select the output or status to check.

Use the Test Condition button to test the condition against live data from Power BI.

Connect the true path and/or the false path to a subsequent node (at least 1 output required).

Approval

Pauses the workflow and sends a message to an organization member. The workflow only continues after that person makes a decision (human-in-the-loop).

• Choose a decision maker from the organization.
• Write a subject and message. Use a variable such as {{aianalyze1.output}} to include data in the message.
• Set a timeout (default 1440 min / 24 hours). On expiry the request is automatically rejected.

The node has two outgoing paths: Approve and Reject.

Actions

Action nodes are endpoints — they have no outgoing connection. A workflow must have at least 1 action node at the end.

Email

Sends an email to one or more recipients.

• Enter the email address, subject, and message body.
• Use variables (e.g. {{aianalyze1.output}}) to include results from previous nodes.

Teams webhook

Sends a message to a Microsoft Teams channel via an incoming webhook.

• Paste the webhook URL of your Teams channel. See the Microsoft guide for creating an incoming webhook via Power Automate Workflows.
• Provide a title and message body.
• Use variables (e.g. {{aianalyze1.output}}) to include results from previous nodes.

Variables

In prompts and messages you can include data from previous nodes using the syntax {{alias.path}}. You set the alias on each node. Example: if a DAX Query node has alias daxquery1, use {{daxquery1.output}} to include the output of that node.

Next step

Go to Run workflow for an explanation of how to run a workflow and view execution history.