Hi @JohnJOSullivan , Thank you for bringing up this subject I'm gonna start off light with a couple of standards that you probably already have..but perhaps they'll be useful for others.  Just for clarity there is no public Fusion API yet.  I'm assuming you are talking about using Fusion for API con...

Great idea @cverges-medallia  +1

@David-M-Allen @KellieGWAB , I don't have any templates around this type of functionality planned at this time.  But you could start from one of the existing templates for ideas.  If I was going to build this using your example David I would start by building out a solid trigger module.  Most likely...

Thanks @MarkKo3 and totally agree.  Where would you want to see that information? In Workfront itself?  Linked from the API Explorer?  In our documentation? Don't care where it is as long as it has the elements needed? Or something else?   Please note I'm asking this to get more clarity for folks to...

Chiming in here @Richard__Carlson and @MarkKo3  Love the thoughts here.  For clarity on this idea...are you looking for standard "native" Workfront Data insights or a place where you can keep track of all of your custom data? Also..is there a place within existing tool areas where you would expect t...

Thanks @skyehansen I'll share with our documentation team.

Thanks @PoppyJennings , I haven't done this before but I am intrigued.   You can set a scenario to create a webhook and an additional scenario to get triggered by that webhook.  In theory that could pass a JSON Payload or a triggered action that could then pull in the JSON payload.   @AndyHess have ...

Great Idea @Viktoriia !  We won't be adding anything to the current Fusion Cookbook but we are strongly considering a new one.  Also we are looking at having a series of different events that cover this and similar topics in the autumn.  

Well folks....that's a wrap! Thank you for reaching out to us and we look forward to catching you next time.  We will make every effort to follow up with any followup responses or anything posted at this point or before.   

True...you don't always need to compare New State with Old State...but sometimes that is needed.   One gotcha with "Changed" (which by the way is a super handy operator) is that you want to make sure it is only looking for Updates and not New and Updates or you'll get double execution.