Create a flow<\/strong><\/h2>\n\n\n\nSo how would it work? You need to create a new flow triggered with an HTTP request. In the body of this request, you\u2019ll pass a flow definition which will be used to generate a flow. Let\u2019s do it step by step.
Create a flow and add a trigger. Take a search for \u2018When a HTTP request is received\u2019. Now it\u2019s time to provide a body schema. The easiest way is to use a sample payload. You can type it literally this way:<\/p>\n\n\n
\n{\n\"flowName\": \"some name\",\n\"flowJson\": \"imagine I'm JSON\"\n}\n<\/pre><\/div>\n\n\n![\"\"](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2019\/01\/1-1.jpg\")
<\/a><\/figure><\/div>\n\n\n\nThe schema is generated. Create a new step and look for \u2018Get Flow\u2019 action. In this action select your environment and any existing flow. You have to create at least one action before you\u2019ll be able to save your work. Give your flow a name and save it. I\u2019ve named it \u2018FlowProvisioner\u2019. Then go back to your \u2018Get Flow\u2019 action and change the selected flow to your flow.<\/p>\n\n\n\n
In the next step, you\u2019ll use \u2018connectionReference\u2019 which is returned by \u2018Get Flow\u2019 action. This variable is necessary to establish a connection from the created flow. You can find your own way of its implementation but the approach I\u2019ve just presented seems to be the best for the purpose of this blog.<\/p>\n\n\n\n
The next action will be \u2018Compose\u2019. Click on the \u2018Inputs\u2019 text field and open \u2018Expression\u2019 tab in the pop-up. Type this expression:<\/p>\n\n\n
\njson(triggerBody()['flowJson'])\n<\/pre><\/div>\n\n\n![\"\"](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2019\/01\/2-1.jpg\")
<\/a><\/figure><\/div>\n\n\n\nIt will convert your input string to a proper JSON object. Let\u2019s use it in the next step. Find a \u2018Create Flow\u2019 step. Select your environment and flow state manually. Chose your input data from dynamic content to fill flow display name and then output from the previous step to fill flow definition field.
In the last section click on the small icon to switch to array input mode. From dynamic content select \u2018connectionReference\u2019 from \u2018Get Flow\u2019 step.
It\u2019s all set. Your flow should work now, but I\u2019d suggest you spend a few more minutes adding some responses and exception handling.<\/p>\n\n\n\n
![\"\"](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2019\/01\/3-1.jpg\")
<\/a><\/figure><\/div>\n\n\n\n<\/div>\n\n\n\nFlow responses<\/strong><\/h2>\n\n\n\nBetween a \u2018Create Flow\u2019 action and \u2018Compose\u2019 use a plus icon to add a parallel branch. Find a \u2018Response\u2019 action and fill it with data. I\u2019d suggest setting the status code to 400 (Bad request). In the body, you can put your message i.e. \u2018flowJson is not a correct json string\u2019. Then click on the three dots icon in the top right corner and \u2018configure run after\u2019 to run only if the previous action failed.<\/p>\n\n\n\n
![\"\"](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2019\/01\/runAfter.gif\")
<\/a><\/figure><\/div>\n\n\n\nCreate a similar action after \u2018Create Flow\u2019 but in this case, it\u2019s good to put some additional data in the body. From the dynamic content pop-up select body of the previous step. There you\u2019ll find information about the reason of the action failure.
It\u2019d be nice to send also a success message. Create a parallel branch after \u2018Create Flow\u2019 and add \u2018Response\u2019 action. You can put a body of the previous step as a body of the response. There is some necessary information about a flow like display name or id. Set the status code to 201 (Created). Flow is ready to use.<\/p>\n\n\n\n
![\"\"](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2019\/01\/5-1024x316-1.jpg\")
<\/a><\/figure><\/div>\n\n\n\n<\/div>\n\n\n\nHow to use it?<\/h3>\n\n\n\n
First of all, we need to get a flow definition. Export a flow which you want to deploy and unzip a file. Open folder \\Microsoft.Flow\\flows\\<your-flow-guid> and open definition.json. Then, copy only a \u2018definition\u2019 property value from the file. It should contain triggers, output and actions data. There is also metadata which isn\u2019t necessary. Escape<\/a> all special characters and then you can use a flow definition in your request.
If you format this JSON, you\u2019ll notice it\u2019s very readable. For instance, let\u2019s take a look at \u2018When an item is created\u2019 trigger. In the property \u2018inputs\u2019 there is a property path.<\/p>\n\n\n\n\u201cpath\u201d:\u201d\/datasets\/@{encodeURIComponent( encodeURIComponent(\u2018<your-tenant>\/sites\/<your-site-name>\u2018))}\/tables\/@{encodeURIComponent( encodeURIComponent(\u201840182f33-da1f-48f3-a4d9-971e89338f5e\u2018))}\/onnewitems\u201d<\/em><\/p>\n\n\n\nHere is the site URL as well as the list GUID. You can make an application which will replace those strings and generate few similar flows for different SharePoint lists and sites.<\/p>\n\n\n\n
The solution described is a perfect instrument for creating few almost exact flows. It is also useful when you want to migrate some flows from one environment to another. In the next blog post, I\u2019ll show you how to create a simple flow to get data flow definition as a JSON. It\u2019ll make the flow transfer even more convenient.
I think this article gives you a solid base to create more complex flows and solutions. If you take time for flow definition analysis, you\u2019ll undoubtedly find patterns, and you\u2019ll be able to develop flows more dynamically.<\/p>\n\n\n
Create a flow and add a trigger. Take a search for \u2018When a HTTP request is received\u2019. Now it\u2019s time to provide a body schema. The easiest way is to use a sample payload. You can type it literally this way:<\/p>\n\n\n
\n{\n\"flowName\": \"some name\",\n\"flowJson\": \"imagine I'm JSON\"\n}\n<\/pre><\/div>\n\n\n<\/a><\/figure><\/div>\n\n\n\nThe schema is generated. Create a new step and look for \u2018Get Flow\u2019 action. In this action select your environment and any existing flow. You have to create at least one action before you\u2019ll be able to save your work. Give your flow a name and save it. I\u2019ve named it \u2018FlowProvisioner\u2019. Then go back to your \u2018Get Flow\u2019 action and change the selected flow to your flow.<\/p>\n\n\n\n
In the next step, you\u2019ll use \u2018connectionReference\u2019 which is returned by \u2018Get Flow\u2019 action. This variable is necessary to establish a connection from the created flow. You can find your own way of its implementation but the approach I\u2019ve just presented seems to be the best for the purpose of this blog.<\/p>\n\n\n\n
The next action will be \u2018Compose\u2019. Click on the \u2018Inputs\u2019 text field and open \u2018Expression\u2019 tab in the pop-up. Type this expression:<\/p>\n\n\n
\njson(triggerBody()['flowJson'])\n<\/pre><\/div>\n\n\n<\/a><\/figure><\/div>\n\n\n\nIt will convert your input string to a proper JSON object. Let\u2019s use it in the next step. Find a \u2018Create Flow\u2019 step. Select your environment and flow state manually. Chose your input data from dynamic content to fill flow display name and then output from the previous step to fill flow definition field.
In the last section click on the small icon to switch to array input mode. From dynamic content select \u2018connectionReference\u2019 from \u2018Get Flow\u2019 step.
It\u2019s all set. Your flow should work now, but I\u2019d suggest you spend a few more minutes adding some responses and exception handling.<\/p>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/div>\n\n\n\nFlow responses<\/strong><\/h2>\n\n\n\nBetween a \u2018Create Flow\u2019 action and \u2018Compose\u2019 use a plus icon to add a parallel branch. Find a \u2018Response\u2019 action and fill it with data. I\u2019d suggest setting the status code to 400 (Bad request). In the body, you can put your message i.e. \u2018flowJson is not a correct json string\u2019. Then click on the three dots icon in the top right corner and \u2018configure run after\u2019 to run only if the previous action failed.<\/p>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\nCreate a similar action after \u2018Create Flow\u2019 but in this case, it\u2019s good to put some additional data in the body. From the dynamic content pop-up select body of the previous step. There you\u2019ll find information about the reason of the action failure.
It\u2019d be nice to send also a success message. Create a parallel branch after \u2018Create Flow\u2019 and add \u2018Response\u2019 action. You can put a body of the previous step as a body of the response. There is some necessary information about a flow like display name or id. Set the status code to 201 (Created). Flow is ready to use.<\/p>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/div>\n\n\n\nHow to use it?<\/h3>\n\n\n\n
First of all, we need to get a flow definition. Export a flow which you want to deploy and unzip a file. Open folder \\Microsoft.Flow\\flows\\<your-flow-guid> and open definition.json. Then, copy only a \u2018definition\u2019 property value from the file. It should contain triggers, output and actions data. There is also metadata which isn\u2019t necessary. Escape<\/a> all special characters and then you can use a flow definition in your request.
If you format this JSON, you\u2019ll notice it\u2019s very readable. For instance, let\u2019s take a look at \u2018When an item is created\u2019 trigger. In the property \u2018inputs\u2019 there is a property path.<\/p>\n\n\n\n\u201cpath\u201d:\u201d\/datasets\/@{encodeURIComponent( encodeURIComponent(\u2018<your-tenant>\/sites\/<your-site-name>\u2018))}\/tables\/@{encodeURIComponent( encodeURIComponent(\u201840182f33-da1f-48f3-a4d9-971e89338f5e\u2018))}\/onnewitems\u201d<\/em><\/p>\n\n\n\nHere is the site URL as well as the list GUID. You can make an application which will replace those strings and generate few similar flows for different SharePoint lists and sites.<\/p>\n\n\n\n
The solution described is a perfect instrument for creating few almost exact flows. It is also useful when you want to migrate some flows from one environment to another. In the next blog post, I\u2019ll show you how to create a simple flow to get data flow definition as a JSON. It\u2019ll make the flow transfer even more convenient.
I think this article gives you a solid base to create more complex flows and solutions. If you take time for flow definition analysis, you\u2019ll undoubtedly find patterns, and you\u2019ll be able to develop flows more dynamically.<\/p>\n\n\n