Logic Apps for visual workflows in Azure - Mini Project: Build & Apply

Logic Apps for Visual Workflows

📖 Scenario: You work in a small company that wants to automate sending a welcome email to new employees. Instead of writing code, you will use Azure Logic Apps to create a visual workflow that triggers when a new employee is added to a SharePoint list.

🎯 Goal: Create a Logic App that triggers on a new SharePoint list item, extracts the employee's name and email, and sends a welcome email automatically.

📋 What You'll Learn

Create a Logic App with a trigger for new SharePoint list items

Add an action to get the employee's name and email from the list item

Add an action to send an email using Office 365 Outlook

Configure the email with a subject and body including the employee's name

💡 Why This Matters

🌍 Real World

Automating business processes without writing code saves time and reduces errors. Logic Apps provide a visual way to connect services like SharePoint and Outlook.

💼 Career

Cloud architects and developers use Logic Apps to build scalable, maintainable workflows that integrate multiple cloud services efficiently.

1

Create the Logic App trigger for new SharePoint list items

In your Logic App designer, create a trigger using When an item is created from the SharePoint connector. Set the Site Address to https://contoso.sharepoint.com/sites/employees and the List Name to NewEmployees.

Azure

# Add the SharePoint trigger with Site Address and List Name
# Your code here

Hint

Use the SharePoint connector trigger named When an item is created and set the site URL and list name exactly as given.

2

Add actions to extract employee name and email

Add an action to get the employee's Name and Email from the SharePoint list item. Use the dynamic content from the trigger to select Name and Email fields.

Azure

{
  "definition": {
    "triggers": {
      "When_an_item_is_created": {
        "type": "ApiConnection",
        "inputs": {
          "host": {
            "connection": {
              "name": "/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Web/connections/sharepoint"
            }
          },
          "method": "get",
          "path": "/datasets/default/tables/NewEmployees/onnewitems",
          "queries": {
            "siteUrl": "https://contoso.sharepoint.com/sites/employees",
            "listName": "NewEmployees"
          }
        },
        "recurrence": {
          "frequency": "Minute",
          "interval": 3
        }
      }
    },
    "actions": {
      "Get_employee_details": {
        "type": "Compose",
        "inputs": {
          "Name": "@triggerOutputs()?['body/Name']",
          "Email": "@triggerOutputs()?['body/Email']"
        }
      }
    }
  }
}
# Your code here to add the Compose action

Hint

Use a Compose action to extract Name and Email from the trigger outputs using expressions.

3

Add an action to send a welcome email

Add an action using the Office 365 Outlook connector called Send an email (V2). Set the To field to the employee's email from the Compose action, the Subject to Welcome to the Company, and the Body to Hello, [Name]! Welcome to the team. where [Name] is the employee's name from the Compose action.

Azure

{
  "definition": {
    "triggers": {
      "When_an_item_is_created": {
        "type": "ApiConnection",
        "inputs": {
          "host": {
            "connection": {
              "name": "/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Web/connections/sharepoint"
            }
          },
          "method": "get",
          "path": "/datasets/default/tables/NewEmployees/onnewitems",
          "queries": {
            "siteUrl": "https://contoso.sharepoint.com/sites/employees",
            "listName": "NewEmployees"
          }
        },
        "recurrence": {
          "frequency": "Minute",
          "interval": 3
        }
      }
    },
    "actions": {
      "Get_employee_details": {
        "type": "Compose",
        "inputs": {
          "Name": "@triggerOutputs()?['body/Name']",
          "Email": "@triggerOutputs()?['body/Email']"
        }
      },
      "Send_welcome_email": {
        "type": "ApiConnection",
        "inputs": {
          "host": {
            "connection": {
              "name": "/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Web/connections/office365"
            }
          },
          "method": "post",
          "path": "/v2/Mail",
          "body": {
            "To": "@outputs('Get_employee_details')?['Email']",
            "Subject": "Welcome to the Company",
            "Body": "Hello, @outputs('Get_employee_details')?['Name']! Welcome to the team."
          }
        }
      }
    }
  }
}
# Your code here to add the Send email action

Hint

Use the Office 365 Outlook connector's Send an email (V2) action. Use dynamic content from the Compose action for the email fields.

4

Finalize and save the Logic App workflow

Add the $schema property with value https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json# at the root of the Logic App definition. This completes the Logic App JSON structure for deployment.

Azure

{
  "definition": {
    "triggers": {
      "When_an_item_is_created": {
        "type": "ApiConnection",
        "inputs": {
          "host": {
            "connection": {
              "name": "/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Web/connections/sharepoint"
            }
          },
          "method": "get",
          "path": "/datasets/default/tables/NewEmployees/onnewitems",
          "queries": {
            "siteUrl": "https://contoso.sharepoint.com/sites/employees",
            "listName": "NewEmployees"
          }
        },
        "recurrence": {
          "frequency": "Minute",
          "interval": 3
        }
      }
    },
    "actions": {
      "Get_employee_details": {
        "type": "Compose",
        "inputs": {
          "Name": "@triggerOutputs()?['body/Name']",
          "Email": "@triggerOutputs()?['body/Email']"
        }
      },
      "Send_welcome_email": {
        "type": "ApiConnection",
        "inputs": {
          "host": {
            "connection": {
              "name": "/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.Web/connections/office365"
            }
          },
          "method": "post",
          "path": "/v2/Mail",
          "body": {
            "To": "@outputs('Get_employee_details')?['Email']",
            "Subject": "Welcome to the Company",
            "Body": "Hello, @outputs('Get_employee_details')?['Name']! Welcome to the team."
          }
        }
      }
    }
  }
}
# Your code here to add the $schema property

Hint

The $schema property is required at the root of the Logic App JSON to define the schema version.

Practice

1. What is the primary purpose of Azure Logic Apps in cloud workflows?

easy

A. To create automated workflows visually without writing code

B. To manually manage virtual machines

C. To store large amounts of data

D. To write complex backend applications

Solution

1. Step 1: Understand Logic Apps purpose

   Logic Apps are designed to automate workflows visually, making it easy to connect services without coding.

2. Step 2: Compare options

   Options B, C, and D describe other Azure services or tasks unrelated to Logic Apps' main function.

3. Final Answer:

   To create automated workflows visually without writing code -> Option A

4. Quick Check:

   Logic Apps = Visual automation [OK]

Hint: Logic Apps automate visually, no code needed [OK]

Common Mistakes:

• Confusing Logic Apps with data storage services
• Thinking Logic Apps manage virtual machines
• Assuming Logic Apps require coding

2. Which of the following is the correct way to start a Logic App workflow?

easy

A. By creating a virtual machine

B. By writing a function in C#

C. By defining a trigger that listens for an event

D. By uploading a database file

Solution

1. Step 1: Identify how Logic Apps start

   Logic Apps begin with a trigger that waits for an event or condition to start the workflow.

2. Step 2: Eliminate incorrect options

   Options B, C, and D are unrelated to Logic Apps workflow initiation.

3. Final Answer:

   By defining a trigger that listens for an event -> Option C

4. Quick Check:

   Logic Apps start with triggers [OK]

Hint: Logic Apps always start with a trigger [OK]

Common Mistakes:

• Thinking code is needed to start Logic Apps
• Confusing Logic Apps with VM or database setup
• Ignoring the trigger concept

3. Consider a Logic App with a trigger on receiving an email and an action to save attachments to OneDrive. What happens when an email with two attachments arrives?

medium

A. Only the first attachment is saved, the second is ignored

B. Attachments are deleted from the email

C. The Logic App fails with an error

D. Both attachments are saved to OneDrive automatically

Solution

1. Step 1: Understand the trigger and action

   The trigger activates on email receipt; the action processes all attachments.

2. Step 2: Analyze behavior with multiple attachments

   Logic Apps handle each attachment, saving both to OneDrive automatically.

3. Final Answer:

   Both attachments are saved to OneDrive automatically -> Option D

4. Quick Check:

   Multiple attachments = all saved [OK]

Hint: Logic Apps process all items in a trigger event [OK]

Common Mistakes:

• Assuming only one attachment is processed
• Expecting failure on multiple attachments
• Thinking attachments get deleted automatically

4. You created a Logic App with a trigger on HTTP request and an action to send an email. The email is never sent after calling the HTTP endpoint. What is the most likely issue?

medium

A. The HTTP trigger URL was not copied correctly

B. The email action is missing a recipient address

C. The Logic App is not connected to a virtual network

D. The Logic App requires a database connection

Solution

1. Step 1: Check trigger and action setup

   The HTTP trigger activates the workflow; the email action must have a recipient to send mail.

2. Step 2: Identify missing email recipient

   If the recipient is missing, the email action silently fails or does not send.

3. Final Answer:

   The email action is missing a recipient address -> Option B

4. Quick Check:

   Email action needs recipient [OK]

Hint: Always set email recipient in Logic Apps [OK]

Common Mistakes:

• Assuming trigger URL copy error causes no email
• Thinking virtual network is required for email
• Believing database connection is needed

5. You want to build a Logic App that triggers when a file is added to an FTP server, then copies the file to Azure Blob Storage, but only if the file size is less than 5 MB. How should you design this workflow?

hard

A. Use an FTP trigger, add a condition to check file size, then copy to Blob Storage if condition is true

B. Use a Blob Storage trigger and copy files to FTP server

C. Use an FTP trigger and copy all files to Blob Storage without conditions

D. Use a manual trigger and upload files to Blob Storage

Solution

1. Step 1: Select correct trigger

   The workflow must start when a file is added to FTP, so use an FTP trigger.

2. Step 2: Add condition to check file size

   Insert a condition action to verify if the file size is less than 5 MB before copying.

3. Step 3: Copy file to Blob Storage if condition met

   If the condition is true, perform the copy action to Azure Blob Storage.

4. Final Answer:

   Use an FTP trigger, add a condition to check file size, then copy to Blob Storage if condition is true -> Option A

5. Quick Check:

   Trigger + condition + action = correct design [OK]

Hint: Use condition to filter files before action [OK]

Common Mistakes:

• Using wrong trigger type
• Skipping file size condition
• Copying files without filtering
• Using manual trigger instead of automatic