Actions are the operations (or API operations) that you can perform on SharePoint by a simple drag and drop and data mapping of elements and values from input trigger, derived values using formulas or desired constant that you may wish to map.
All of the actions that you see below automate what you can do manually on SharePoint.
As shown below, you can Create or Update a file in your SharePoint Document Library based in response to a trigger event.
Set up SharePoint action in your workflow¶
After selecting the action "Create or Update a file" as shown in the above figure, you can continue to configure or set up your action parameter that will define what file you will create or update in SharePoint. You can also construct the content of the file being created or updated using values for the input trigger event.
Select a site from the sites you have access to where you want to create or update a file. If you do not see your site, refer to this page.
Document Library Path
Select the target Document Library from the dropdown. You can also use the Evaluate functionality to map the Path of your Document Library which will be evaluated when the flow is running. While using Evaluate, you can enter either the Use Server relative URL e.g.
/Shared Documents/Test/ or the complete path e.g.
Enter filename that will be created or updated as a result of this action. You can type in a filename or construct the filename using input trigger values or a combination of constants and input trigger values combined using excel style formulas.
Choose file update operation
If the file with the specified file name already exists, you can choose to either append text to an existing text file or overwrite the file. If the file does not exist, Connect will create a new file.
Here you can construct the text that you want your file to be created or updated with. Just like all other text inputs, this filed is made powerful by excel style functions and sophisticated Data Mapping and Transformation capabilities on Connect iPaaS. You can create a text block, which is populated with values from your trigger application. For example in Figure. 2 above, the "Editor" and "Author" are populated from input trigger values.