Hallo David,
this information is 8-10 months old, so it could have changed in the meantime...
But when we started with AEM Assets and wanted to setup the native integration, I had several sessions with an Adobe professional.
Since the AEM Assets application in Fusion didn't offer a lot of functionality and apparently still doesn't, we used the AEM Custom API call module in combination with the Workfront Custom API module.
![lgaertner_0-1713511896041.png lgaertner_0-1713511896041.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/72932i0A556601AC8B74B2/image-size/medium?v=v2&px=400)
The response is processed in a Create JSON module using the following Data structure:
![lgaertner_1-1713512066206.png lgaertner_1-1713512066206.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/72933i2B2B0F0D45A0346B/image-size/medium?v=v2&px=400)
The most tricky part is the setup of the JSON module:
![lgaertner_3-1713513058746.png lgaertner_3-1713513058746.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/72935iE15DD5EC21EAD88E/image-size/medium?v=v2&px=400)
Especially the fields documentProviderID and the externalStorageID.
Unfortunately I do not find, where I found the documentProviderID, but I remember, that this can be found using the api-unsupported.
I will add a solution, if I find it.
Finally the custom API call on Workfront looks like this:
![lgaertner_2-1713512987356.png lgaertner_2-1713512987356.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/72934i91C7022E2B38F1AD/image-size/medium?v=v2&px=400)
Perhaps this helps.
Regards
Lars