Review the Application Password Update Trigger

Review the application-password update trigger carefully because its raw arguments may include credential data that must not be logged or sent externally.

The Update App Password trigger is listed in the WordPress User group in the AI Agent Workflows editor. It starts a workflow when WordPress fires the wp_update_application_password hook.

Screenshot to add: [Workflow editor showing the Update App Password trigger]

When this trigger fires

This hook relates to an application-password credential change. Treat the event payload as sensitive until you verify exactly which arguments are passed and stored.

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. Other scalar arguments may remain in the payload; inspect a sample before mapping fields.

Security warning: the inspected normalizer wraps raw hook arguments without general credential redaction, and workflow run records persist trigger payloads. Because this hook may carry credential data, do not activate it on a production site until the source is changed and verified to remove secrets before persistence.

Configure the trigger

  1. Open the workflow in the visual editor and open the node picker.
  2. Select WordPress, then User, and add Update App Password.
  3. Inspect a captured sample to understand the available arguments. This catalog entry has no user-specific filter field.
  4. Save and test with controlled data. Forward only the information required by later steps.

Source hook

Catalog hook: wp_update_application_password. This guide is based on the supplied source code; live execution has not been tested.