What is an Automated Cloud Flow in Power Automate? Explain with a Gmail flow

 🤖 Automated Cloud Flow

• Automated Cloud Flow in Power Automate: A workflow that triggers automatically based on a specific event (e.g., receiving an email, a file upload, or a database update).
• It connects apps and services to perform tasks without manual intervention, streamlining repetitive processes.

📧 Example: Gmail Automated Flow

• Scenario: Automatically save email attachments to OneDrive and send a confirmation reply.

🪜 Step-by-Step Flow Creation:

• 🔔 Trigger:
  • "When a new email arrives (V3)" (Gmail connector).
• ⚙️ Configure:
  • 📁 Folder: Inbox
  • 🔍 Filter: Only emails with attachments (optional).
• 🧰 Initialize Variable (Optional):
  • Store the sender’s email address for later use.
• 📎 Get Attachments:
  • 🎬 Action: "Get attachments (V3)" (Gmail connector).
  • This extracts attachments from the email.
• ☁️ Save to OneDrive:
  • 🔄 Loop through each attachment using "Apply to each":
    • 🎬 Action: "Create file" (OneDrive connector).
    • ⚙️ Set:
      • 📂 Folder path: e.g., /Attachments/
      • 🏷️ File name: Attachment name (dynamic content).
      • 📄 File content: Attachment content (dynamic content).
• 📧 Send Confirmation Email:
  • 🎬 Action: "Send email (V3)" (Gmail connector).
  • ⚙️ Configure:
    • 👤 To: Sender’s email address (dynamic content).
    • 📃 Subject: "Attachment saved: [Original Subject]"
    • 📝 Body: "Your file was saved to OneDrive. Thank you!"

🧩 Key Components:

• ⏱️ Triggers: Start the flow automatically (e.g., new Gmail email).
• 🎬 Actions: Tasks performed post-trigger (e.g., save files, send emails).
• 🔗 Connectors: Link services like Gmail, OneDrive, etc.
• 📦 Dynamic Content: Data from previous steps (e.g., sender’s email, attachment name).

✨ Benefits:

• ⏱️ Time-Saving: No manual downloading/forwarding.
• 💯 Accuracy: Reduces human error in repetitive tasks.
• 📈 Scalability: Handles multiple emails/attachments effortlessly.

By setting up this flow, you ensure every email attachment is instantly saved to the cloud, and the sender receives an automated confirmation.

Note: Ensure Gmail and OneDrive accounts are connected to Power Automate with proper permissions. Use filters to avoid processing irrelevant emails.

Dynamic Content example flow IN Power Automate

 📄 Flow Scenario:

• We'll create a flow:
  • Triggers when a new item is added to a SharePoint list.
  • Sends an email notification about the new item.

🪜 Flow Steps:

• 🔔 Trigger: "When an item is created" (SharePoint)
  • This starts the flow when a new item is added to a SharePoint list.
• 📧 Action: "Send an email (V2)" (Outlook 365)
  • This action sends an email message.

📦 Dynamic Content in Action:

• The "Send an email (V2)" action uses Dynamic Content.

📤 Trigger Output (Dynamic Content):

• The "When an item is created" trigger provides SharePoint item info as Dynamic Content:
  • 🏷️ Title (of the item)
  • 📧 Created By Email
  • 📅 Modified Date
  • 🔗 Link to item

📧 Using Dynamic Content in the Email Action:

• In "Send an email (V2)":

  • To: Fixed email, or Dynamic Content from a "Assigned To" field (if available).

  • Subject: "New item created: [Title]" ([Title] is Dynamic Content)

  • Body:

    A new item has been created in the SharePoint list.
    
    Title: \[Title]
    Created by: \[Created By Email]
    Modified Date: \[Modified Date]
    You can view the item here: \[Link to item]
    

    • (Again, [Title], [Created By Email], [Modified Date], [Link to item] are from Dynamic Content)

💡 Explanation:

• Power Automate knows the "When an item is created" trigger provides data.
• It offers this data as Dynamic Content.
• You choose which Dynamic Content to use in actions.

✨ Benefits:

• ⏱️ Automation: Emails send automatically.
• 🧑‍ Personalization: Emails include item-specific info.
• 📈 Efficiency: No manual copying/pasting.

Input Parameters and Dynamic Content In power automate

 📥 Input Parameters

• What they are: Input parameters are like ➡️ tunnels that pass data into your Power Automate flow from an external source. This source could be:
  • 📱 Power Apps
  • 🔄 Another flow (child flow)
  • 🔘 A button you click
• Why they're useful:
  • ♻️ Make your flows reusable: Provide values when the flow runs, not hardcoded.
  • 🔧 Increase flexibility: Adapt flow behavior based on input data.
• Example:
  • Imagine a flow to create tasks in a project tool. You could use input parameters to specify:
    • 🏷️ Task title
    • 📝 Task description
    • 🧑‍🤝‍🧑 Assigned user
    • 📅 Due date
  • This way, the same flow creates many tasks with different details.

📦 Dynamic Content

• What it is: Dynamic content is data available from the trigger and actions within your flow. It's the output of previous steps for use in later steps.
• Why it's useful:
  • 🚚 Automate data transfer: Automatically move data between apps/services.
  • 🧑‍ Personalize actions: Tailor actions (e.g., include a customer's name in an email).
• Example:
  • Consider a flow triggered when a new item is added to a SharePoint list:
    • The trigger ("When an item is created") provides dynamic content like:
      • 🏷️ Item title
      • 📧 Created by
      • 📅 Modified date
      • 🆔 List item ID
    • You can then use this content in actions:
      • 📧 Email notification: include item title and creator.
      • 📁 Create a file: use item ID in the filename.

↔️ Key Differences and Relationship

• Input parameters:
  • ➡️ Data into the flow
  • 📍 Defined in the trigger
• Dynamic content:
  • ⬅️ Data from the trigger and actions
  • ⚙️ Used in actions
• Relationship:
  • ➡️ Input parameters can become dynamic content.
  • ⛽ Dynamic content "fuels" the actions in your flow.

Running and Testing Your Flow in Power Automate

 🏃 Running and Testing Your Flow ✅

Once you've created your Power Automate Flow, it's crucial to run and test it to ensure it works as expected. Here's how:

• Saving Your Flow 💾

  • Before running, always save your flow by clicking the "Save" button (usually in the top right corner).

• Testing Options 🧪 Power Automate provides several ways to test your flows:

  • Manual Testing (for Instant Flows) 👆

    • If your flow has a manual trigger (like a button click), you can simply run it by:
      • Going to your "My flows" page.
      • Finding your flow.
      • Clicking the "Run" button (the play icon).
      • Following any prompts that appear.

  • Automatic Testing (using recent triggers or sample data) ⚙️

    • When you click "Test" (usually in the top right corner of the flow editor):
      • You might see an option to use data from a recent successful run of the flow (if it's an automated flow).
      • You might be prompted to provide sample data to simulate a trigger event. This is very useful for automated flows.

  • Manual Testing (for Automated Flows - triggering the event) 🚦

    • For automated flows, the most common way to test is to actually perform the action that triggers the flow. For example:
      • If the trigger is "When a new email arrives," send a test email that meets your trigger conditions.
      • If the trigger is "When a file is added to SharePoint," upload a test file.

• Monitoring Your Flow Runs 👀 After running a test, you can monitor the flow's execution:

  • Go to your "My flows" page.
  • Click on your flow.
  • Under "Run history," you'll see a list of recent runs.
  • Click on a specific run to see the details of each step, including:
    • The status (Succeeded, Failed, Running).
    • The inputs and outputs of each action.
    • Any error messages if the flow failed.

• Troubleshooting Failed Runs 🛠️ If your flow fails:

  • Click on the failed run in the "Run history."
  • Examine the steps to see which one failed (it will be marked with a red "Failed" status).
  • Review the error message provided for that step. This usually gives you clues about what went wrong (e.g., incorrect permissions, missing data, service outages).
  • Edit your flow to fix the identified issue and test again.

• Iterative Testing 🔄 Testing is often an iterative process. You might need to run your flow multiple times, make adjustments, and test again until it works perfectly for your intended scenario.

By diligently running and testing your Power Automate Flows, you can ensure they are reliable and effectively automate your tasks! 👍

Creating a Power Automate Flow from Scratch

 📧 Creating a Power Automate Flow: Sending Gmail Message

Here's how to create a flow that sends a Gmail message:

1. Create a New Flow 🆕

   • 💻 Go to the Power Automate website (make.powerautomate.com).
   • ➕ Select "Create."
   • ⚡ Choose "Instant cloud flow" (for manual triggering) or "Scheduled cloud flow" (for timed sending), or "Automated cloud flow" (if you want to trigger it from another event). For this example, we'll use "Instant cloud flow".
   • 🖱️ Give your flow a name (e.g., "Send Gmail").
   • 🔘 Select "Manually trigger a flow" as your trigger and click "Create".

2. Add the Gmail Action 📧

   • ➕ Click "New step."
   • 🔍 Search for "Gmail."
   • ➡️ Select the "Send an email (V2)" Gmail action.

3. Configure the Gmail Action ⚙️

   • 🔗 Sign in: You will be prompted to sign in to your Gmail account and grant Power Automate permission to access it.
   • 👤 To: Enter the recipient's email address.
   • 📄 Subject: Enter the subject of your email.
   • 📝 Body: Enter the content of your email.
   • 📎 Attachments (Optional): If you want to add attachments, you can add them from other connectors, or static files.

4. Test the Flow ✅

   • 💾 Save your flow.
   • ▶️ Click "Test" in the top right corner.
   • 🔘 Select "Manually" and then click "Test".
   • 🏃 Run the flow.
   • 👀 Check your Gmail "Sent" folder and the recipient's inbox to confirm the email was sent successfully.

5. Important Considerations ⚠️

   • 🔐 Security: Be mindful of the permissions you grant to Power Automate.
   • 📝 Error Handling: Add actions to handle potential errors (e.g., sending a notification if the email fails to send).
   • ⚙️ Dynamic Content: You can use dynamic content from previous steps to personalize your email (e.g., adding a name, or information from a database) if you are using a automated flow.
   • 📎 Attachment Size: Be aware of Gmail's attachment size limits.