The WP Authenticate trigger is listed in the WordPress User group in the AI Agent Workflows editor. It starts a workflow when WordPress fires the wp_authenticate hook. The exact timing follows that hook; not every user-related hook represents a completed account change.
Screenshot to add: [Workflow editor showing the WP Authenticate trigger]
When this trigger fires
This trigger maps to wp_authenticate, an authentication hook. Its arguments may contain a username and password, so treat the payload as highly sensitive.
Event data and privacy
User-trigger payloads use source, event, and hook arguments under args. WordPress user objects are converted to basic fields such as ID, login, email, and display name, but other scalar arguments may remain in the payload. Inspect a sample before mapping values.
Security warning: the inspected normalizer wraps raw hook arguments without general credential redaction, and workflow run records persist trigger payloads. Because this hook may receive login credentials, do not activate it on a production site until the source is changed and verified to remove secrets before persistence.
Configure the trigger
- Open the workflow in the visual editor and open the node picker.
- Select WordPress, then User, and add WP Authenticate.
- Inspect a captured sample to understand the hook arguments. This catalog entry has no user-specific filter field.
- Save and test only with controlled data. Avoid storing or forwarding credentials and other sensitive account information.
Source hook
Catalog hook: wp_authenticate. This article is based on the supplied source code; it does not claim that a live event was tested.