This is a known problem with how Fusion/Make.com deal with webhooks.  It has no way to, for example, allow JWT or OAuth 2.0 to allow for proper security.  If you know the webhook URL or the static header values in use, you can call it.  JWT would be much more proper in 2025+.  I'd suggest you file a...

The event will be in the EVENT table in Data Connect, if you have access to that.  Otherwise, check the Journal to see if they're captured there.  Finally, there may be a NOTE object created by the system and attached to the Document object that you could look at.

OMG that totally worked!  It's nuts, the UI accepts "2w" but to your point, it only does the calculation properly with "10d".  It looks from that link like the "w" means "day of week", which is bonkers.

I'm looking to setup two tasks -- one for "Meeting" and another for "Schedule Meeting".  I'd like the "Schedule Meeting" one to dynamically start 2 weeks prior to the "Meeting" task, which has other dependencies on the rest of the project.I've tried a number of different options related to both pred...

We don't use rates, but looking at the PROJ object in https://developer.adobe.com/workfront/api-explorer/, there's a collection on it for "rates".  I imagine you'd do a POST to the PROJ/{id} object and set the rates in the body.I recommend setting a project just like you want it and then use a GET P...

Fusion (make.com) uses a pass-by-value mechanism.  As such, you need to create an array object inside a Set Variable using the {{emptyarray}} syntax before the iterator, then use a Get Variable inside the iterator followed by a Set Variable to "override" the variable with the appended array.

The Workfront API Explorer (https://developer.adobe.com/workfront/api-explorer/) gives a list of the objects that are officially supported.  I'm not aware of any kinda of "metadata" APIs that would indicate things like Workfront license package purchased, number of licenses available vs. used vs. pu...

You don't.  Do the loop, but put in a filter condition right after the loop starts that prevents further execution once you've exceeded the condition you're after.

Why not just use the API to do a /count operation?  Count all proofs with a non-complete status.  When 0, proceed to process the task from there.