When user profile updated in WordPress, send the profile data to a webhook URL

Whenever a WordPress user profile is updated, FlowMattic posts that user’s current profile data as JSON to a webhook URL you set, so an outside system stays in step with your site’s accounts.

WordPress

Webhook Outgoing

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.4k sites Free to import

The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

If another system keeps its own copy of your members or customers, such as a CRM, a support desk or an in-house database, it goes stale every time someone edits their WordPress profile. This workflow sends the profile to that system's webhook each time it changes, so the other side can update its record.

The WordPress User Profile Updated trigger fires when a user profile is updated. That covers a user saving their own profile, an administrator editing an account and a plugin updating user data through WordPress. FlowMattic passes the user's details as they are after the update. It doesn't send the old values or a list of what changed.

The Webhook Outgoing Submit Data to Webhook step then sends a POST request in JSON format to the URL you choose. It ships unmapped: after import you enter the receiving system's webhook URL and map the user fields you want to send, such as the user ID, email and display name.

Include the user ID or email in the data so the receiving system can find the matching record. Edit a test user and check Task History for the response the webhook URL returned.

Keeping a CRM copy current

A membership site sends profile changes to its CRM's incoming webhook, so a new email address or name a member saves reaches the CRM record.

Syncing a support desk

A software company posts updated WordPress profiles to its help desk's webhook, so agents see the customer's current details on tickets.

Feeding a data warehouse

A publisher's data team receives every profile update at an internal endpoint and stores it to track account changes over time.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
WordPress User Profile Updated
Fires when a WordPress user profile is updated, by the user, an administrator or a plugin. The user's details after the update are passed to the webhook step.
Step 2Action
Webhook Outgoing Submit Data to Webhook
Sends a POST request with JSON data to the webhook URL you enter. Nothing is mapped in the template, so add the URL and map the WordPress user fields the receiving system needs.

What you need

FlowMatticCore

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Always map the WordPress user ID into the outgoing data. It never changes, unlike the email, so the receiving system can match the right record.
To send only certain accounts, put a Filter between the User Profile Updated trigger and the webhook step that continues for the roles you sync, such as customer or member.
Match the key names in your outgoing data to what the receiving system's documentation expects, so each value lands in the right field.

Questions about this workflow

Does the webhook receive the old WordPress profile values?

No. The trigger passes the user's details as they are after the update. If the receiving system needs to know what changed, it has to compare with the copy it already holds.

Do profile edits made by administrators start this workflow?

Yes. Any update to a user profile fires the trigger, whether the user saves it, an administrator edits it in the dashboard or a plugin updates it.

Can I secure the data posted to the webhook URL?

Use an HTTPS URL for the receiving system and follow its own instructions for authentication. Check Task History after a test edit to see how it responded.