Expand my Community achievements bar.

Don’t miss the Workfront AMA: System Smarts & Strategic Starts! Ask your questions about keeping Workfront running smoothly, planning enhancements, reporting, or adoption, and get practical insights from Adobe experts.

Fusion Workfront Webhook filter User isActive not working

Avatar

Level 4

Hi All,

I've got a Workfront webhook as the first module of a Fusion scenario. The scenario is meant to run when the Home Team of an active Workfront user is updated - but it's not working.

Here's how it's configured:

Record type: User
State: New state
Filters:
        HomeTeamID Changed 
        AND IsActive EQUAL true
AND connection updates included
Record Origin: Updated Record Only

When I update an active user's Home Team, the webhook is not called so the scenario does not run.

I did some testing and figured that the issue is caused by the filter IsActive EQUAL true.

If I create a webhook withouth that filter, it just works fine. (Obviously it is also called when an inactive user's Home Team is updated - which is not what I want.)

Record type: User
State: New state
Filters:
        HomeTeamID Changed 
AND connection updates included
Record Origin: Updated Record Only

 Can someone please tell me what is wrong with this filter?

tibormolnar_0-1757708418295.png

Thank you,

Tibor

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

5 Replies

Avatar

Level 3

Hi @tibormolnar 

 

I'm no expert at Fusion, but I have run into this before and user "Equal to (case insensitive)" and had it work. 

Alex_Di_0-1757709195398.png

 

Avatar

Level 4

Hi @Alex_Di ,

thank you for the response. However, it seems that the "Equal to (case insensitive)" operator option isn't available for isActive in a webhook config:

tibormolnar_0-1757709939950.png

So, I tried both IsActive EQUAL TRUE and IsActive EQUAL True, but neither of these work.

Avatar

Level 4

Can you try using "true" from keywords in General functions? What I had noticed in the past is that when you type 'true' or 'false', it sends it as a text, whereas a keyword is sent as a boolean. While they both work the same in the regular search module, a webhook might be more sensitive.

Screenshot 2025-09-15 at 10.10.01 AM.pngScreenshot 2025-09-15 at 10.17.48 AM.pngScreenshot 2025-09-15 at 10.18.08 AM.png

Avatar

Level 4

Hi @SuryaLakhani,

thank you for the idea. It sounds reasonable but unfortunately, it doesn't work either. I tested it.

The webhook is not triggered when I update an active user.

tibormolnar_0-1758007562583.png tibormolnar_1-1758007574366.png

tibormolnar_2-1758007894649.png

 

 

Avatar

Level 4

This has been raised with Adobe. I will post here when I receive their feedback.