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.

Practice

1. What is the first step in a basic workflow in a no-code platform?

easy

A. Setting a trigger to start the workflow

B. Adding multiple actions at once

C. Testing the workflow after completion

D. Sharing the workflow with others

Solution

1. Step 1: Understand the role of a trigger

   A trigger is what starts the workflow automatically when a specific event happens.

2. Step 2: Identify the first action in workflow setup

   Before adding actions, you must set the trigger to tell the system when to run the workflow.

3. Final Answer:

   Setting a trigger to start the workflow -> Option A

4. Quick Check:

   Trigger starts workflow = Setting a trigger [OK]

Hint: Workflows always begin with a trigger event [OK]

Common Mistakes:

• Thinking actions come before triggers
• Skipping the trigger setup
• Confusing testing with starting

2. Which of the following is the correct way to add an action in a no-code workflow?

easy

A. Drag and drop an action after the trigger

B. Click the trigger and select 'Add action'

C. Write code to define the action

D. Restart the workflow to add actions

Solution

1. Step 1: Understand how actions are added in no-code tools

   No-code platforms usually allow dragging and dropping actions to build workflows visually.

2. Step 2: Identify the correct method among options

   Dragging and dropping an action after the trigger is the standard way to add actions without coding.

3. Final Answer:

   Drag and drop an action after the trigger -> Option A

4. Quick Check:

   Actions added by drag and drop = Drag and drop an action after the trigger [OK]

Hint: Add actions by dragging them after the trigger [OK]

Common Mistakes:

• Trying to write code in no-code tools
• Clicking the trigger to add actions
• Restarting workflow to add actions

3. Consider a workflow triggered when a new email arrives. It has two actions: save attachment and send notification. What happens when an email without attachment arrives?

medium

A. The workflow crashes with an error

B. The workflow saves an empty file and sends notification

C. The workflow stops and sends no notification

D. The workflow skips saving attachment but sends notification

Solution

1. Step 1: Analyze workflow actions with missing data

   If the email has no attachment, the save attachment action usually skips or does nothing.

2. Step 2: Understand notification action behavior

   The send notification action still runs because it is independent of attachment presence.

3. Final Answer:

   The workflow skips saving attachment but sends notification -> Option D

4. Quick Check:

   No attachment skips save, notification still sent = The workflow skips saving attachment but sends notification [OK]

Hint: Actions run unless blocked; missing data skips that action [OK]

Common Mistakes:

• Assuming workflow stops on missing data
• Thinking empty files are saved
• Believing workflow crashes on missing attachment

4. A workflow is set to send a welcome email when a user signs up, but no emails are sent. What is the most likely error?

medium

A. The workflow was tested successfully

B. The trigger is not set to user signup event

C. The workflow has too many actions

D. The email action is placed before the trigger

Solution

1. Step 1: Check the trigger setup

   If no emails are sent, the trigger might not be correctly set to detect user signup.

2. Step 2: Verify action order and workflow logic

   Actions cannot come before triggers; too many actions do not stop sending; successful test contradicts no emails.

3. Final Answer:

   The trigger is not set to user signup event -> Option B

4. Quick Check:

   Missing trigger causes no action = The trigger is not set to user signup event [OK]

Hint: Check trigger event if workflow actions don't run [OK]

Common Mistakes:

• Placing actions before triggers
• Blaming number of actions
• Ignoring trigger misconfiguration

5. You want to create a workflow that automatically tags incoming support tickets as 'urgent' if the message contains the word 'immediately' and sends an alert. Which approach best achieves this?

hard

A. Set a trigger on ticket update and send alert without conditions

B. Manually check each ticket and tag urgent ones

C. Use a trigger on new ticket, add a condition to check message text, then tag and alert actions

D. Create a workflow that tags all tickets as urgent regardless of content

Solution

1. Step 1: Define the trigger and condition

   The workflow should start when a new ticket arrives and check if the message contains 'immediately'.

2. Step 2: Add actions based on condition

   If the condition is true, the workflow tags the ticket as 'urgent' and sends an alert automatically.

3. Final Answer:

   Use a trigger on new ticket, add a condition to check message text, then tag and alert actions -> Option C

4. Quick Check:

   Trigger + condition + actions = Use a trigger on new ticket, add a condition to check message text, then tag and alert actions [OK]

Hint: Combine trigger, condition, and actions for targeted automation [OK]

Common Mistakes:

• Skipping condition and tagging all tickets
• Relying on manual checks
• Triggering on wrong event