+ Title: "Package Power Automate flows into organizational list templates"

+recommendations: true

+audience: Admin

+f1.keywords:

+- NOCSH

+ms.localizationpriority: medium

+search.appverid:

+- SPO160

+- MET150

+- M365-collaboration

+description: "Learn how to package biz apps into organizational list templates."

+# Package Power Automate flows into organizational list templates

+There are a number of steps by which you can create a packaged SharePoint list template that contains in-built custom flows. The objective is to assemble and register a packaged file that contains the site script actions needed to create the list and the flows, and a Dataverse solution archive (zip) that contains the flow definitions.

+Once you have your source SharePoint list set up and are ready to work on integrating flows with it, and on assembling a template with these components, perform the following the steps:

+## Obtaining the Dataverse solution zip file

+1. Sign in to Power Automate portal by launching [https://flow.microsoft.com](https://flow.microsoft.com) (or choose **Integrate > Power Automate > See your flows**" in the SharePoint Portal).

+1. Create a new Dataverse solution by referring to [Overview of solution-aware flows](/power-automate/overview-solution-flows).

+ For an introduction to Dataverse solutions, see [Solution concepts](/power-platform/alm/solution-concepts-alm).

+1. Add a new flow or customize existing flows to this solution by referring to [Create a cloud flow in a solution](/power-automate/create-flow-solution).

+1. Ensure that your flows use connection references for each trigger and action that you use. For more information on how to use a connection reference, see [Use a connection reference in a solution](/power-apps/maker/data-platform/create-connection-reference).

+1. Once you are satisfied with the contents of your solution (including any connection references or environment variables you wish to set up), [export and download](/power-automate/export-flow-solution) it to a disk.

+1. Extract all files from the zip file into a separate folder.

+1. Browse into the folder's **Workflows** subfolder.

+1. Open each flow-related .json file and then search and replace all instances of the following elements:

+ 1. **The URL of the SharePoint site that the original list resided in**: Replace with **{ContextSharePointSiteUrl}**.

+ 1. **The ID of the original SharePoint list**: Replace with **{ContextSharePointListId}**.

+ **For example** [Before replacements]:

+ "parameters": {

+ "dataset": "https://microsoft.sharepoint-df.com/teams/AlinTest ",

+ "table": "d6ac2804-7a1c-4cd4-98c8-56b85a9294b7"

+ }

+ **For example** [After replacements]:

+ "parameters": {

+ "dataset": "{ContextSharePointSiteUrl}",

+ "table": "{ContextSharePointListId}"

+ }

+10. Save the changes and close all file editors that you've opened for these files.

+11. Go back to the root folder of the solution; select all files (solution.xml, customizations.xml, and so on) and folders; right-click and choose **Compress to ZIP file** from the context menu.

+ :::image type="content" source="media/select-all-files-compress-to-zip-file.png" alt-text="Screenshot that shows selecting all the files and compressing them to a zip." lightbox="media/select-all-files-compress-to-zip-file.png":::

+

+ You can keep this resulting zip file, and you can also choose to discard the original solution zip file that earlier downloaded (as specified in Step 6 of this procedure).

+## Obtaining the site script action file (manifest.json)

+> [!IMPORTANT]

+> Prior to performing the steps in this section, ensure that you've tested your prototype list and flow(s) to your satisfaction.

+1. Ensure you've installed SharePoint Online Management Shell on your computer.

+1. Launch SharePoint Online Management Shell.

+1. Run the following command to connect to the tenant's admin service:

+ `Connect-SPOService -Url <Link to SharePoint admin portal> -Credential <full username of the admin user>`

+4. Run the following command to extract a site script file from the target list:

+ `Get-SPOSiteScriptFromList -ListUrl <full URL of the target list> | Out-File manifest.json`

+5. Open the *manifest.json* file in your favorite text (or code) editor and manually add an action with the verb "importBusinessApps", the relative path of your solution file inside the overall template package and the target listName (in this case, the title of the listName binding). This value should be the same as the *listName* property of the "CreateSPList" action.

+ For example:

+ :::image type="content" source="media/adding-verb-json-file.png" alt-text="Screenshot that shows adding a verb in the .json file." lightbox="media/adding-verb-json-file.png":::

+## Assembling the final SharePoint package zip file

+1. Ensure that the solution zip file and the *manifest.json* file (from previous step) are in the same folder location.

+1. Select these two files; right-click and then select **Compress to ZIP file** (or **Send to > ZIP file**, depending on the OS).

+## Registering the new template as a list design

+1. To upload the zip file (created in [Assembling the final SharePoint package zip file](#assembling-the-final-sharepoint-package-zip-file)) as a site script package, run the following command in the same management shell window:

+ `$pkg = Add-SPOSiteScriptPackage -Title "<script title>" -Description "<script description>" -ContentPath '<relative path to zip file from previous step>'`

+ > [!NOTE]

+ > Inclusion of the *Description* property in the command is optional.

+2. Take a peek at the new package by printing out its properties through the following command:

+ `"$pkg"`

+ The output should contain an *Id* property which is needed in the following step(s).

+ > [!NOTE]

+ > (Optional) Run `Get-SPOListDesign` to ensure you're not adding a duplicate with the same title/description, or to simply inspect what's already there.

+3. Run the following command:

+ `Add-SPOListDesign -Title "<list design title>" -Description "<list design description>" -SiteScripts $pkg.Id`

+ If the list design was successfully created, you should be able to view it in the **From your organization**" area of the **Create List** dialog.

+## Related topics

+[Connect-SPOService](/powershell/module/sharepoint-online/connect-sposervice)

+[Get-SPOSiteScriptFromList](/powershell/module/sharepoint-online/get-spositescriptfromlist)

+[Add-SPOSiteScriptPackage](/powershell/module/sharepoint-online/add-spositescriptpackage)