Logic Apps for visual workflows in Azure - Step-by-Step Execution

Process Flow - Logic Apps for visual workflows

Start Logic App Trigger

↓

Evaluate Trigger Condition

↓

Run Actions

↓

Check Action Results

↓

End or Loop/Retry

Logic Apps start with a trigger, then run actions if conditions are met, and finally end or wait for the next trigger.

Execution Sample

Azure

Trigger: When HTTP request received
Action 1: Get file content
Action 2: Send email with file
Condition: If file exists
End

This Logic App waits for an HTTP request, then gets a file and sends it by email if the file exists.

Process Table

Step	Action	Input	Condition Check	Result	Next Step
1	Trigger fires	HTTP request received	N/A	Trigger activated	Run Action 1
2	Get file content	File path from trigger	N/A	File content retrieved	Check if file exists
3	Condition check	File content	File exists?	Yes	Run Action 2
4	Send email	File content	N/A	Email sent	End Logic App
5	End	N/A	N/A	Workflow complete	Wait for next trigger

💡 Logic App ends after sending email and waits for the next trigger.

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
TriggerStatus	Not fired	Fired	Fired	Fired
FileContent	Empty	Loaded	Loaded	Loaded
ConditionResult	Unknown	Unknown	True	True
EmailStatus	Not sent	Not sent	Not sent	Sent

Key Moments - 2 Insights

Why does the Logic App wait after the trigger if the condition is not met?

Because as shown in step 3 of the execution_table, if the condition 'File exists?' is No, the Logic App does not run the email action and waits for the next trigger.

What happens if the trigger never fires?

The Logic App stays idle and does not run any actions, as the trigger is the starting point (step 1). No further steps execute without it.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after Step 2?

A File content retrieved

B Trigger activated

C Email sent

D Workflow complete

💡 Hint

Check the 'Result' column for Step 2 in the execution_table.

At which step does the Logic App check if the file exists?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Condition Check' column in the execution_table.

If the file does not exist, what happens next according to the execution flow?

A Send email anyway

B End Logic App immediately

C Wait for next trigger without sending email

D Retry getting file content

💡 Hint

Refer to the concept_flow and step 3 in the execution_table where condition is checked.

Concept Snapshot

Logic Apps start with a trigger that listens for events.
They run actions in order, based on conditions.
Conditions decide if next actions run or wait.
Workflows end or wait for next trigger.
Visual design helps build and understand flow.

Full Transcript

Logic Apps are visual workflows in Azure that start when a trigger event happens, like receiving an HTTP request. Once triggered, the Logic App runs actions step-by-step. For example, it can get file content and then check if the file exists. If the file exists, it sends an email with the file. If not, it waits for the next trigger without sending the email. Variables like TriggerStatus and FileContent change as the workflow runs. This flow helps automate tasks without writing code, using a clear visual design.