Retrieve Metadata of a Web Page using Power Automate Desktop

Retrieve Metadata of a Web Page using Power Automate Desktop

This Power Automate Desktop flow allows the user to enter a website URL and automatically retrieves important metadata such as the page title, meta keywords, description, and the full HTML source. It uses browser automation to open the page, extract information, and optionally save the source code to a file.

Step-by-step Explanation

  1. Ask the user for a website URL
    The flow begins with an input dialog that prompts the user to enter the website address. The entered URL is stored in the variable URL. If the user clicks Cancel, the remaining steps do not execute.
  2. Open the website in Microsoft Edge
    If the user clicks OK, the flow launches Edge and opens the provided webpage. The browser window is maximized, and a retry mechanism is added in case the page fails to load on the first attempt.
    ⚠️ The Power Automate browser extension must be installed for this to work.
  3. Retrieve the title of the webpage
    The action GetDetailsOfWebPage → Title extracts the webpage title and displays it in a message box to the user.
  4. Retrieve the meta keywords
    The flow then extracts the webpage’s meta keywords.
    • If keywords exist → Show them in a message box
    • If keywords do not exist → Inform the user that no keywords are specified
  5. Retrieve the meta description
    The description is extracted next. Similar to keywords:
    • If description exists → Display it
    • If not → Show a “No description” message
  6. Ask if the user wants to save the HTML source
    A Yes/No dialog asks whether to save the page’s HTML source locally.
    • If the user selects No, the flow skips to the last step.
    • If the user selects Yes, a file selection dialog appears:
    The user can choose an existing file or type a new file name (e.g., pagecode.txt).
  7. Save the HTML source to a local file
    If a file is selected and the user did not press Cancel:
    • The entire HTML source is extracted using DetailsType: Source.
    • The content is written into the chosen file.
    • If the file already exists, it will be overwritten.
  8. Close the browser
    After all metadata has been retrieved, the flow safely closes the Edge browser window.

Full Power Automate Desktop Code

# The 'Display input dialog' action prompts you to enter the address of the website you want to retrieve the metadata from.
Display.InputDialog Title: $'''Get metadata of a web page''' Message: $'''Please provide the web page address that you want to examine:''' DefaultValue: $'''https://mspowerplatformtips.blogspot.com/''' InputType: Display.InputType.SingleLine IsTopMost: True UserInput=> URL ButtonPressed=> ButtonPressed

# The following 'If' action checks whether the 'Cancel' button was pressed.
IF ButtonPressed <> $'''Cancel''' THEN

    /# Launch the webpage in Edge and retrieve metadata.
    Please note that the Power Automate browser extension is required for this flow to work.#/
    WebAutomation.LaunchEdge.LaunchEdge Url: URL WindowState: WebAutomation.BrowserWindowState.Maximized ClearCache: False ClearCookies: False Timeout: 60 BrowserInstance=> Browser
    ON ERROR REPEAT 1 TIMES WAIT 2
    END

    WebAutomation.GetDetailsOfWebPage BrowserInstance: Browser DetailsType: WebAutomation.DetailsType.Title Details=> WebPageTitle
    Display.ShowMessageDialog.ShowMessage Title: $'''Get metadata of a webpage.''' Message: $'''The title of the given web page is:

%WebPageTitle%'''

    WebAutomation.GetDetailsOfWebPage BrowserInstance: Browser DetailsType: WebAutomation.DetailsType.MetaKeywords Details=> WebPageKeywords
    IF IsNotEmpty(WebPageKeywords) THEN
        Display.ShowMessageDialog.ShowMessage Title: $'''Get metadata of a webpage.''' Message: $'''The keywords specified for the given web page are:

%WebPageKeywords%'''
    ELSE
        Display.ShowMessageDialog.ShowMessage Title: $'''Get metadata of a webpage.''' Message: $'''No keywords specified for the web page:
%URL%'''
    END

    WebAutomation.GetDetailsOfWebPage BrowserInstance: Browser DetailsType: WebAutomation.DetailsType.Description Details=> WebPageDescription
    IF IsNotEmpty(WebPageDescription) THEN
        Display.ShowMessageDialog.ShowMessage Title: $'''Get metadata of a webpage.''' Message: $'''The description for the given web page is:

%WebPageDescription%'''
    ELSE
        Display.ShowMessageDialog.ShowMessage Title: $'''Get metadata of a webpage.''' Message: $'''No description specified for the web page:
%URL%'''
    END

    Display.ShowMessageDialog.ShowMessage Title: $'''Do you want to save HTML source? ''' Message: $'''Do you want to save the HTML source of the given webpage locally?
Web page URL: %URL%''' Buttons: Display.Buttons.YesNo ButtonPressed=> SaveSourceButton
    IF SaveSourceButton = $'''Yes''' THEN

        Display.SelectFileDialog.SelectFile Title: $'''Select a text file to save HTML source into or provide a new name''' FileFilter: $'''*.txt''' CheckIfFileExists: False SelectedFile=> SelectedFile ButtonPressed=> FileSelectedButtonPressed

        IF FileSelectedButtonPressed <> $'''Cancel''' THEN
            WebAutomation.GetDetailsOfWebPage BrowserInstance: Browser DetailsType: WebAutomation.DetailsType.Source Details=> WebPageSource
            File.WriteText File: SelectedFile TextToWrite: WebPageSource AppendNewLine: True IfFileExists: File.IfFileExists.Overwrite Encoding: File.FileEncoding.Unicode
        END
    END

    WebAutomation.CloseWebBrowser BrowserInstance: Browser
END

Comments

Post a Comment

Popular posts from this blog

Part 1: Creating Code Apps in Power Apps - A step-by-step guide (with real errors I faced & how I fixed them)

Image
Intro In this post I’ll walk you through how I set up a code-based app for Power Apps (React/Vite front-end + Power Platform CLI for packaging/deployment), the exact errors I ran into, and how I solved them. If you want a hands-on, copy-paste able guide that covers Node versions, pac auth, environment issues, and packaging tips, this is for you. Prerequisites Microsoft 365 account with access to a Power Platform environment Node.js ( 20.19+  recommended LTS) VS Code Install power platform tools extension in VS Code. Steps: Step 1 : Open Visual Studio Code and launch the integrated terminal. Step 2: In the terminal, run the following commands one by one.   mkdir D:\CodeApps - Force cd D:\CodeApps npm create vite @latest myfirstapp -- -- template react - ts cd D:\CodeApps\myfirstapp npm install Initially, I ran the command: npm create vite@latest MyFirstApp -- --template react-ts This gave the error: Invalid package.json name The issue was caused because package...
Read more

Calling Microsoft Graph API from Power Automate Using Azure App Services – Step-by-Step Guide

Image
Step 1: You should have an Azure subscription, or if you have access to the Microsoft Entra Admin Center, you can create an app from there. This app can then be used in Power Automate to connect to Microsoft Graph API. Step 2: Click on "New registration" , provide a name for your app, assign the required API permissions (such as Microsoft Graph permissions), and then click "Register" to complete the app registration process. Step 3: After registration, you'll be redirected to the app's overview page. From there, navigate to the API permissions tab and click "Add a permission" to assign the necessary Microsoft Graph API permissions. Step 4: Select Microsoft Graph as the API, and based on your requirements, choose the appropriate permissions. In my case, I selected Application permissions , which do not require user sign-in and are suitable for background services or automation. Step 5: Select the required Microsoft Graph API permissions. Yo...
Read more

Step-by-Step Guide: Power Automate Custom Connector Using Graph API from Azure App Service

Image
Step 1: Open Power Automate, navigate to the Custom Connectors tab, and select Create from blank as shown in the image below. custom connector(click image for better resolution) Step 2: In the General tab, upload an icon (less than 1MB), add a description, select the correct scheme (in my case, HTTPS ), and provide the host name. For example, if your API URL is https://graph.microsoft.com/v1.0/users/{email} , the host name will be the highlighted part — graph.microsoft.com . Step 3: Go to the Security tab. Here, you need to select the authentication method. Choose OAuth 2.0 as the authentication type, as shown in the image below. Step 4: Select the Identity Provider as Azure Active Directory . Check the box Enable Service Principal Support . This option allows you to create a connection using a Client ID and Client Secret instead of using the user's own authentication. Next, provide the Client ID , Client Secret , Tenant ID , and other required details as shown in t...
Read more