The Edit User trigger is listed in the WordPress User group in the AI Agent Workflows editor. It starts a workflow when WordPress fires the edit_user_profile hook. The exact timing follows that hook; it should not be assumed to mean a completed account change unless the hook itself confirms that.
Screenshot to add: [Workflow editor showing the Edit User trigger]
When this trigger fires
The catalog label is Edit User, but the registered hook is edit_user_profile, a profile-screen hook. Treat it as a profile display/setup event, not proof that user data was saved.
Event data and privacy
User-trigger payloads use a general structure containing source, event, and the hook’s arguments under args. WordPress user objects are converted to basic fields such as user ID, login, email, and display name. The exact argument structure varies by hook, so inspect a sample in the editor before mapping values.
Configure the trigger
- Open the workflow in the visual editor and open the node picker.
- Select WordPress, then User, and add Edit User.
- Inspect a captured sample to identify the available arguments. The source defines no user-specific filter field for this catalog entry.
- Save and test with a controlled event. Use only the fields needed by later nodes and avoid forwarding sensitive account data.
Source hook
Catalog hook: edit_user_profile. This guide describes the supplied plugin registration; live execution has not been tested.