Hi Daniel,
A follow up to this; it also appears that any action on the member can trigger webhook. The description of the trigger implied to me that it would action when something changed on the member's account. The action on the member's side seems to consistently trigger the zap, however admin actions still have the same behaviour described in the above comment. When a member does something that triggers the zap, the system seems to go back and capture the changes that happened prior to that action.
From testing, the following actions can form part of the "Member Edited in Community" trigger:
Logging in/last activity updating
Creating or replying to a post
Getting points
Watching a post/topic/forum
I feel like there is room for a zap trigger that looks to see when a member's account information is updated; not every action that member takes. By this, I mean having the capacity to trigger a zap based on when a member edits their email address, a member's primary or secondary group changes, etc. rather than the entire activity of the account.
The problem with having it action every time a member does anything is that it is causing a significantly greater amount of actions than necessary when member edits are relatively infrequent, but member discussion is highly common.
Thank you,
Zac