{"id":36814,"date":"2023-12-21T14:58:49","date_gmt":"2023-12-21T09:28:49","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=36814"},"modified":"2023-12-27T15:01:41","modified_gmt":"2023-12-27T09:31:41","slug":"custom-actions-with-power-automate-desktop-flows","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2023\/12\/custom-actions-with-power-automate-desktop-flows\/","title":{"rendered":"Custom Actions with Power Automate Desktop Flows"},"content":{"rendered":"

Introduction<\/h2>\n

A custom action in desktop flow is a feature designed to automate repetitive tasks seamlessly.
\nThis blog provides a comprehensive guide on designing and leveraging custom actions in the desktop version of Power Automate flows. The journey starts with a step-by-step procedure to create these custom actions, offering a detailed walkthrough of the process to upload them within the desktop Power Automate flows environment.<\/p>\n

Certainly! In this scenario, a custom action in the desktop flow is employed to automatically download files linked to various activities. Whether these files are attachments or stored in notes, the custom action streamlines the process, offering users the flexibility to choose a personalized destination path for efficient file organization. This automation enhances efficiency, saves time, and empowers users with control over their file management preferences.<\/p>\n

Pre-requisite:<\/strong> To create custom action in Power Automate for desktop flows you need the following things:<\/p>\n

1. NET Framework 4.7.2 SDK or above.<\/p>\n

2. Visual Studio 2022 or above<\/p>\n

3. Power Automate desktop v2.32 or above.<\/p>\n

4. The Action SDK<\/p>\n

Step 1:<\/strong> Create a custom action<\/strong><\/p>\n

Open Visual Studio 2022 -> Create sample project -> Go to Tools -> Nugget Package Manager -> Package Manager Console.<\/p>\n

\"Custom<\/p>\n

Run the below commands inside the NuGet Package Console.<\/p>\n

Action SDK:
\nNuGet\\Install-Package Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK -Version 1.4.232.23122-rc<\/strong><\/p>\n

\"Custom<\/p>\n

Power Automate desktop \u2013 Visual Studio templates:<\/p>\n

dotnet new install Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.Templates::1.0.0-rci<\/p>\n

\"Custom<\/p>\n

Create a new power automate project as mentioned below.<\/p>\n

\"Custom<\/p>\n

Once a project is created successfully, you can proceed with the code. In this illustration we have written \/used the below code however it may vary depending upon the use case or the actual scenario.<\/p>\n

using System;<\/em>\r\n\r\nusing System.IO;<\/em>\r\n\r\nusing Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK;<\/em>\r\n\r\nusing Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.Attributes;<\/em>\r\n\r\nnamespace Modules.CustomActions<\/em>\r\n\r\n{<\/em>\r\n\r\n\u00a0\u00a0\u00a0 [Action(Id = \"Action1\", Order = 1, FriendlyName = \"Custom Action\", Description = \"The action is used to download notes\/attachments\")]<\/em>\r\n\r\n\u00a0\u00a0\u00a0 [Throws(\"ActionError\")] \/\/ TODO: change error name (or delete if not needed)<\/em>\r\n\r\n\u00a0\u00a0\u00a0 public class Action1 : ActionBase<\/em>\r\n\r\n\u00a0\u00a0\u00a0 {<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #region Properties<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ File path where the downloaded file will be stored<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [InputArgument(FriendlyName = \"File Path\", Description = \"File Path\")]<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public string filepath { get; set; }<\/em>\r\n\r\n\u00a0<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ File path where the downloaded file will be stored<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [InputArgument(FriendlyName = \"Document Body\", Description = \"document Body\")]<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public string documentBody { get; set; }<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ The name of the file to be created<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [InputArgument(FriendlyName = \"File Name\", Description = \"File Name\")]<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public string fileName { get; set; }<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #endregion<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #region Methods Overrides<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ Override of the Execute method in the base class<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public override void Execute(ActionContext context)<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 {<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 try<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 {<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ Concatenate the file path and file name<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 filepath = filepath + \"\\\\\" +fileName;<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ Create a file stream to write the file data<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 using (FileStream data = File.Create(filepath))<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 {<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ Convert Base64 document body to byte array<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 byte[] fileBytes = Convert.FromBase64String(documentBody);<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ Write the byte array to the file stream<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 data.Write(fileBytes, 0, fileBytes.Length);<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 catch (Exception e)<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 {<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ Handle exceptions and throw an ActionException<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 if (e is ActionException) throw;<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 throw new ActionException(\"ActionError\", e.Message, e.InnerException);<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/em>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 #endregion<\/em>\r\n\r\n\u00a0\u00a0\u00a0 }<\/em>\r\n\r\n}<\/em><\/pre>\n
 <\/p>\n
Build the project.<\/p>\n
Step 2<\/strong>: Creating and importing a self-signed certificate<\/strong><\/p>\n
Open Windows PowerShell.<\/p>\n
\"Custom<\/p>\n
Copy and paste the following commands, replacing the underlined names as appropriate.<\/p>\n
$certname = \"CustomActionCertificate\"<\/u>\r\n$cert = New-SelfSignedCertificate -CertStoreLocation Cert:\\CurrentUser\\My -Type CodeSigningCert -Subject \"CN=$certname\" -KeyExportPolicy Exportable -KeySpec Signature -KeyLength 2048 -KeyAlgorithm RSA -HashAlgorithm SHA256\r\n\r\n$mypwd = ConvertTo-SecureString -String \"pass@word1\"<\/u> -Force -AsPlainText\r\n\r\nExport-PfxCertificate -Cert $cert -FilePath \"D:\\Task\\Blog\\CustomActionCertificate.pfx<\/u>\" -Password $mypwd<\/pre>\n
\"Custom<\/p>\n
After generating and exporting the certificate, incorporate it into your trust root. Then, double-click on the exported certificate. Kindly complete all the steps in import vizard.<\/p>\n
Click Next<\/strong><\/p>\n
\"Custom<\/p>\n
\"Custom<\/p>\n
Write down the password that was used in the certificate creation command.<\/p>\n
\"Custom<\/p>\n
In the certificate store, select ‘Trusted Root Certification Authorities.’ Then click on ‘Next,’ and after that, simply click on ‘Finish.’ You will receive a message indicating that the import was successful.<\/p>\n
\"Custom<\/p>\n
Step 3:<\/strong> – Sign the .dl<\/strong>l file using a trusted certificate by running the following command in a Developer Command Prompt for Visual Studio, replacing names as appropriate.<\/p>\n
Signtool sign \/f “D:\\Task\\Blog\\CustomActionCertificate.pfx<\/u>” \/p pass@word1<\/u> \/fd SHA256 “D:\\Task\\Blog\\Modules.CustomActions\\Modules.CustomActions\\bin\\Debug\\net472\\Modules.CustomActions.dll<\/u>”<\/p>\n
Step 4: – Packaging everything in a cabinet file<\/p>\n
The .dll containing the custom actions and all its dependencies (.dll files) must be packaged in a cabinet file (.cab).<\/p>\n
Create a Windows PowerShell Script (.ps1) containing the following lines & save it as Script[makeCabFile.ps1].<\/p>\n
param(<\/em>\r\n\r\n[ValidateScript({Test-Path $_ -PathType Container})]<\/em>\r\n\r\n[string]<\/em>\r\n\r\n$sourceDir,\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/em>\r\n\r\n[ValidateScript({Test-Path $_ -PathType Container})]<\/em>\r\n\r\n[string]<\/em>\r\n\r\n$cabOutputDir,<\/em>\r\n\r\n[string]<\/em>\r\n\r\n$cabFilename<\/em>\r\n\r\n)<\/em>\r\n\r\n$ddf = \".OPTION EXPLICIT<\/em>\r\n\r\n.Set CabinetName1=$cabFilename<\/em>\r\n\r\n.Set DiskDirectory1=$cabOutputDir<\/em>\r\n\r\n.Set CompressionType=LZX<\/em>\r\n\r\n.Set Cabinet=on<\/em>\r\n\r\n.Set Compress=on<\/em>\r\n\r\n.Set CabinetFileCountThreshold=0<\/em>\r\n\r\n.Set FolderFileCountThreshold=0<\/em>\r\n\r\n.Set FolderSizeThreshold=0<\/em>\r\n\r\n.Set MaxCabinetSize=0<\/em>\r\n\r\n.Set MaxDiskFileCount=0<\/em>\r\n\r\n.Set MaxDiskSize=0<\/em>\r\n\r\n\"<\/em>\r\n\r\n$ddfpath = ($env:TEMP + \"\\customModule.ddf\")<\/em>\r\n\r\n$sourceDirLength = $sourceDir.Length;<\/em>\r\n\r\n$ddf += (Get-ChildItem $sourceDir -Filter \"*.dll\" | Where-Object { (!$_.PSIsContainer) -and ($_.Name -ne \"Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.dll\") } | Select-Object -ExpandProperty FullName | ForEach-Object { '\"' + $_ + '\" \"' + ($_.Substring($sourceDirLength)) + '\"' }) -join \"`r`n\"<\/em>\r\n\r\n$ddf | Out-File -Encoding UTF8 $ddfpath<\/em>\r\n\r\nmakecab.exe \/F $ddfpath<\/em>\r\n\r\nRemove-Item $ddfpath<\/em><\/pre>\n
Step 5:<\/strong> – Use the following command to create a .cab file in PowerShell.<\/p>\n
.\\makeCabFile.ps1 “D:\\Task\\Blog\\Modules.CustomActions\\Modules.CustomActions\\bin\\Debug\\net472” “D:\\Task\\Blog” CustomActions.cab<\/u><\/p>\n
Step 6:<\/strong> – The .cab file must also be signed. Use the following command to sign the .cab file in a Developer Command Prompt for Visual Studio, replacing names as appropriate.<\/p>\n
Signtool sign \/f “D:\\Task\\Blog\\CustomActionCertificate.pfx” \/p pass@word1 \/fd SHA256 “D:\\Task\\Blog\\CustomActions.cab”<\/p>\n
Step 7:<\/strong> Upload custom actions<\/strong><\/p>\n
Go to Power Automate -> More -> Discover all -> Data -> Custom Action.<\/p>\n
\"Custom<\/p>\n
Select ‘Upload custom action’ and upload the .cab file. However, note that we can upload .cab files up to 30MB.<\/p>\n
\"Custom<\/strong><\/p>\n

\nStep 8:<\/strong> Use custom actions
\n<\/strong>
\nYou can include custom actions in the desktop flow through the ‘Assets library’ using Power Automate Desktop Designer.<\/p>\n
\"Custom<\/p>\n
To use the ‘Assets library,’ select it in the designer. Alternatively, use the Tools bar.<\/p>\n
\"Custom<\/p>\n
In the Assets library, we can see all the custom actions we have uploaded. We can add a custom action, and we can also remove previously added custom actions.<\/p>\n
\"Custom<\/p>\n
Now, we can use our custom action.<\/p>\n
\"Custom<\/p>\n
Double-click on the custom action to add it.<\/p>\n
\"Custom<\/p>\n
Here, documentBody<\/strong> and FileName<\/strong> are variables taking input from the cloud flow. Choose the file path where you want to store the downloaded attachment or notes.<\/p>\n
\"Custom<\/p>\n
We created an automated cloud flow that triggers when a file is added to notes. Then, we check if the document is present or not in a condition. If the document is present, we call a desktop flow, select the run mode, and pass documentBody and fileName.<\/p>\n
\"Custom<\/p>\n
Here, I am adding a docx file to the note.<\/p>\n
\"Custom<\/p>\n
Finally, the file is downloaded or stored in my selected path automatically<\/p>\n
Conclusion<\/strong><\/h2>\n
Thus, we learned how to utilize the custom actions with the Power Automate Desktop Flows<\/p>\n
\"Microsoft<\/a><\/p>\n
 <\/p>\n
<\/pre>\n","protected":false},"excerpt":{"rendered":"
Introduction A custom action in desktop flow is a feature designed to automate repetitive tasks seamlessly. This blog provides a comprehensive guide on designing and leveraging custom actions in the desktop version of Power Automate flows. The journey starts with a step-by-step procedure to create these custom actions, offering a detailed walkthrough of the process\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1913,44],"tags":[1975],"class_list":["post-36814","post","type-post","status-publish","format-standard","hentry","category-microsoft-power-platform-services","category-power-apps","tag-power-automate"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/36814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=36814"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/36814\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=36814"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=36814"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=36814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}