We use Power Automate with workflows within Workfront. I wasn't involved in the setup, but it works pretty nicely. What information are you looking for?
Power Automate does not have any pre-built connectors for Workfront. We use the Workfront API in a custom connector. Our custom connector was built by a developer at a third party consultant - PowerApps911.
Yes. It's been 100% reliable (as long as there aren't any incidents or maintenance with the Workfront event subscription) and worked well for what we needed. We looked in to Fusion but didn't want to make the commitment to Workfront for an iPaaS tool.
Hi - I'm no means a developer so the custom connector was a ton of trial and error and even then, I could only get an action created (Still haven't gotten Triggers to works).
However, Power Automate also does HTTP calls. So I've been playing around with that a little, but you can use only really use that for more static calls.
Like I have one where I wanted to get items updated after Sept 30th on a certain project
https://fcb.my.workfront.com/attask/api/v9.0/optask/search?apiKey=Insert API Key&projectID=Insert Project ID&lastUpdateDate=2020-09-03T15:45:00:000&lastUpdateDate_Mod=gt&fields=description,status
Then I use the parse tool and the other Power Automate tools to do the other stuff I wanted.
Hope that helps
@Anthony Imgrund‚ : cool stuff! I'm exited to give it a try!
Have you found a tutorial/reference on what is possible with HTTP calls or do I need to go purely trial-and-error?
I didn't see anything on PA about the restrictions of HTTP. I think as long as it works in a browser, it works in the tool. I mostly used Workfront's API documentation (and some help from my Assigned Support Engineer) to get things setup. Like the fact I needed to add the apiKey to the URL to authenticate correctly. The best part is that you can test out your URL right in the browser itself to make sure it works before you put in PA.