Skip to main content
Transfer Files from Asite platform via Microsoft Power Automate

This article helps you understand how to transfer files from Asite using Microsoft Power Automate (Flow).

Updated over a month ago

Below is an example to understand how to transfer files from Asite to an external service called 'Microsoft Sharepoint' via Microsoft Power Automate. Similarly, you can transfer files from Asite to other external services like Box, Projectwise and so on:

1. Create a worklow trigger with 'Task' set as 'Microsoft Flow'. You can configure this workflow trigger on any 'Event' - for example 'Upload Files' - with 'Task Mode' set to 'Post'.

2. Next, go to Microsoft Power Automate homepage https://make.powerautomate.com/en-us/ and sign in using your Microsoft credentials.

3. The Microsoft Power Automate homepage will appear. Click on 'My Flows' from the left menu.


If logging in for the very first time, you might be asked to select country/region as required.

4. Flows created by you will appear if any. Click on 'New flow' to create a new flow.

5. Under 'New Flow', select 'Instant Cloud Flow' option.

6. The screen to build an instant cloud flow will appear along-with available options on how to trigger the flow. Click 'Skip' as this is not required specifically for our integration.

7. A list of connectors and triggers will appear. You can use the search option to enter a keyword and search for your required connector / trigger.

8. To use the connector provided by Asite, search for ‘Asite’ and select the required connector provided by Asite. All Asite connectors are categorized under ‘Premium’ tab (also available in ‘All’ tab).

9. Triggers and Actions for selected 'Asite' connector will appear in separate tabs.

'Actions' tab to view available actions that can be performed when above trigger is executed.

10. Select a trigger as required to perform an action when a specific Asite workflow event is triggered based on configuration within Asite. Here, we are selecting 'When a workflow is triggered on file(s)'.

11. You will be required to authorize your access to Asite in the next step by signing in. Click on 'Sign In'. This is only one time process.

12. Enter your Asite login credentials and click 'Login'.

13. Here, you need to allow Microsoft Power Automate to read document and write document by clicking on 'Allow'. This is required only for one time.

14. After your Asite account access is granted, you can search and select project name and workflow trigger name. Only those triggers in which 'Microsoft Flow' has been defined as task in 'Post' task mode will be listed.

Once done, click '+ New Step' to continue.

15. You are required to choose an action here.

16. To use the connector provided by Asite, search for ‘Asite’ and select the required connector provided by Asite. All Asite connectors are categorized under ‘Premium’ tab (also available in ‘All’ tab).

17. Actions tab lists out all the actions that can be performed when above trigger is executed.

Actions available currently for 'Asite' connector are:

Set File Metadata - Click here to obtain the steps of defining file's metadata.

Create File - Click here to obtain the steps to upload a file in other system via Asite connector

Get File Content - Click here to obtain the steps to download a file.

Please note that 'Set File Metadata' is mandatory before you can perform 'Create File' action.


18. Let's download a file by using action 'Get File Content'

Now, select 'Get File Content' as the action to be performed when above trigger is executed.

19. It will open a text box for entering Download File URL.

20. Click on the text box to see available options. A popup screen would appear with tabs named 'Dynamic Content' and 'Expression'.

21. Under 'Dynamic Content', use the search option 'Search dynamic content' to search for 'direct link'. Dynamic Content option enables you to pull dynamic values i.e. variables from Asite in this scenario. From the results, select 'DirectLink' and continue.

22. The selected 'DirectLink' will auto populate in the 'URL Selection' field. This direct link will enable pushing the file content from Asite to selected external service depending on the configuration. At this stage, pushing of files with limited size upto 100 MB are only supported via Microsoft Flow.

Once done, click '+ New Step' to continue.


23. Now, let's upload a file to other tool - Sharepoint by using action 'Create File'

For this we need to upload this file to Sharepoint. In this step, we need to select the connector provided by Sharepoint. Use the search option to find the required connector.

24. In this example, we will search and select 'Sharepoint' connector.

25. Once the connector is selected, relevant actions will be listed. We are selecting 'Create File' in this example. Use the search or scroll option to find your concerned trigger.

26. In the 'Create File' step, enter details as follows:

Site Address - Search and select a Sharepoint site address from the available dropdown option.

Folder Path - Click on the folder icon and select concerned folder where the file needs to be saved.

File Name - Search and select 'FileName' from the dynamic content popup.

File Content - Search and select 'File' from the dynamic content popup.

27. Click 'Save' to continue.

28. The newly created flow will start appearing in the listing.

The required configuration is done for transferring files from Asite to Sharepoint as per above steps. You can now test the scenario by uploading file as per the folder configured in the relevant workflow trigger within Asite.

29. The flow run history will appear under '28-day run history' once the file is uploaded as follows. It displays flow start date and time, duration and status.

30. Click on start date and time to view details regarding the running flow.

The green ticks indicate that particular step of the flow got executed successfully. Click on the respective titles within the flow to get further details.

31. As the flow was successful, the file would become available in Sharepoint as per the folder path configured in step 27 above.


Check: FAQs


Did this answer your question?