Extract a data table from an email with power automate desktop

[Natron26]

I receive emails daily that have information in the form of a data table, i have attached a sample of what it looks like.  Any suggestion how i would extract the data table into a data table variable or just take certain information from the datable since I don't need all the information.

 

[lbendlin]

Are these emails in HTML format?  Can you post a sample email body contents?

[Natron26]

Good Morning what do you need as far as the sample email body contents?

[lbendlin]

the HTML - specifically the part that describes the table.

[Natron26]

How should i do that to make it easier for you?

[Natron26]

I was able to go through the emails and retrieve the data, i only need certain information.  My idea now is to pull the get the data and then use a regular expression to extract the wanted information. I'm not sure how to use regular expressions in Power automate yet.  Below is a sample of the information that will be coming through and all the email will be structured this way.  Can you help with creating a regular expression to pull the text that are in bold from the text string?  

opportunity: CLMS – Natron Publications
Account: Brady 101
Contract Months : 42
Subscription Term : Man
Closed Date : 7/7/2023
Total Contract Value : $45
Owner : Kirk Cousins
Billing Term :
Billing Contact Name 1 : Aron Rogers
Billing Contact Email 1 : nothing@yahoo.com

Billing Contact Name 2 : Patrick Mahomes
Billing Contact Email 2 :
Email for Invoices : hello at yahoo.com
Billing Mailing Address : 900 Half way house
Client PO Number :

[lbendlin]

You can certainly go the regexp route. I would think parsing the HTML is easier as you can address the DOM elements directly.

[Natron26]

Can you provide a workflow?

[lbendlin]

Can you provide a sample HTML?

[Natron26]

How do i provide a HTML?

[AlexEncodian]

@Natron26 

Do you have to use PAD? You can do this using PA.

Encodian’s Utility - Parse HTML Table action converts the data in an HTML table into JSON for use within a flow. It'll be easier to parse using native PA expressions and loops.

  
FYI – Encodian actions with the “Utility“ prefix only consume 1/20th of Encodian action count (apart from on free plan). For example, a Standard plan has 500 actions (so utility actions can be used 500x20 = 10,000 times)  
 
---- 
*Encodian Flowr is a Standard Power Automate connector with 100+ actions to supercharge flow builds. Conversion, merging, splitting, OCRing, data extraction, QR/Bar codes, searching and much more. And we just added "Utility" actions, which are almost free to use and accelerate solution builds and remove maintenance overheads with actions like Extract text between values, extract URLs, extract email addresses, Password/GUID/HMAC creation, escaping/unescaping HTML, parsing HTML tables, etc.