Action to move Workfront Documents into an AEM Linked Folder via WF Connector (or even HTTP request)

[#1]

Description - Please enable a way to us to automate the moving of regular Workfront documents (i.e. local in the Project) into an AEM Linked Folder via the API (preferably a Fusion action module).

Why is this feature important to you - It's laborious and prone-to-error for users to manually drag and drop Workfront Documents into an AEM Linked Folder. We have many clients where this could be a big time-saver both in terms of reducing the effort to move files and also improving the accuracy of where they place them as we could automate that based on Document metadata.

How would you like the feature to work -  Have a Workfront module in Fusion where we can map in the Document ID and also the ID of the (Linked) Folder or its associated Linked Folder ID it is to be moved into. Even if we have to use a Workfront Custom API call or plain old HTTP Request that would be fine as long as it is via a Production API.

Current Behaviour - There are various internal API calls we have tried to emulate via Fusion and there is an experience league article from last year with a accepted answer post from @VictorTo2 (please note that the original question is not relevant...only the answer) which indicates it was possible at that time but I've been unable to get that to work yet. And, even if I did, it is an unsupported internal API call which is not ideal for production use by customers. So, basically there is no current workaround.

[#2]

This can already be achieved using the information provided in the accepted answer post: moveToFolder - similar to drag and drop in the ui - has been supported in the API since v18.0 and sendDocumentsToExternalProvider - similar to selecting an asset, picking a location in the modal and then sending the AEM - since v19.0.

The initializeStatelessDocumentProviderForUser to establish a doc provider for the tech account is still in unsupported, though this is not the same as internal only and is a one-off action per environment/account combo; you'll find the action in the api explorer

[#3]

Hi @Pete-Worth Thank you for the info. Any chance this can be written up somewhere in a more step by step manner with examples in Fusion (preferably) or Postman?  This seems like a common need and having people try and piece it together means a lot won't be successful. 

Whilst the actions are listed in the API explorer it doesn't provide detail in terms of where to get values from and what the prerequisites are re authentication etc.  At this point I need to find some more time to try it all again based on the latest info graciously provided by Victor.  I consider myself a fairly technical person and this is not as straight-forward as I would hope.....ideally having a Fusion connector action to do this OOTB.