Basic workflows and actions in No-Code - Step-by-Step Execution

Concept Flow - Basic workflows and actions

Start Workflow

↓

Trigger Event

↓

Perform Action 1

↓

Perform Action 2

↓

Check Condition?

No→End Workflow

Yes↓

Perform Conditional Action

↓

End Workflow

A workflow starts with a trigger, then performs a series of actions, optionally checks a condition, and ends.

Execution Sample

No-Code

Trigger: New email received
Action 1: Save attachment
Action 2: Send notification
Condition: Attachment size > 5MB
Action 3: Alert admin

This workflow reacts to a new email, saves its attachment, sends a notification, and alerts admin if the attachment is large.

Analysis Table

Step	Event/Condition	Result	Action Taken	Next Step
1	New email received	True	Save attachment	Step 2
2	Attachment saved	Success	Send notification	Step 3
3	Notification sent	Success	Check attachment size > 5MB	Step 4
4	Attachment size > 5MB?	False	Skip alert admin	Step 5
5	Workflow ends	-	-	-

💡 Workflow ends after all actions complete or condition check fails.

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Email Received	No	Yes	Yes	Yes	Yes
Attachment Saved	No	Yes	Yes	Yes	Yes
Notification Sent	No	No	Yes	Yes	Yes
Attachment Size > 5MB	Unknown	Unknown	Unknown	False	False
Admin Alert Sent	No	No	No	No	No

Key Insights - 3 Insights

Why does the workflow stop after checking the condition if it is false?

Because the condition 'Attachment size > 5MB?' is false at Step 4, the workflow skips the conditional action and proceeds to end, as shown in the execution_table row 4.

What triggers the first action in the workflow?

The trigger event 'New email received' at Step 1 starts the workflow and causes the first action 'Save attachment' to run, as seen in the execution_table row 1.

Why is the 'Admin Alert Sent' variable still 'No' at the end?

Because the condition to send the alert was false, the action to alert admin never ran, so 'Admin Alert Sent' remains 'No' as tracked in variable_tracker.

Visual Quiz - 3 Questions

Look at the execution table, what action happens at Step 2?

A Check attachment size

B Save attachment

C Send notification

D Alert admin

💡 Hint

Refer to execution_table row 2 under 'Action Taken'

At which step does the workflow decide not to alert the admin?

A Step 3

B Step 4

C Step 5

D Step 1

💡 Hint

Check execution_table row 4 for the condition result and action taken

If the attachment size was greater than 5MB, what would change in the variable tracker?

A 'Admin Alert Sent' would change to 'Yes'

B 'Notification Sent' would change to 'No'

C 'Attachment Saved' would change to 'No'

D 'Email Received' would change to 'No'

💡 Hint

Look at variable_tracker row for 'Admin Alert Sent' and consider the condition in execution_table row 4

Concept Snapshot

Basic workflows start with a trigger event.
They perform a series of actions in order.
Conditions can control if some actions run.
Workflow ends after all actions or when stopped by a condition.
Variables track progress and results.

Full Transcript

A basic workflow begins when a trigger event happens, such as receiving an email. Then, it performs actions step-by-step, like saving an attachment and sending a notification. Sometimes, it checks a condition to decide if more actions should run, for example, alerting an admin if the attachment is large. If the condition is false, the workflow skips that action and ends. Variables keep track of what has happened at each step, helping to understand the workflow's progress and outcome.