You can use webhooks in Customerly to send data back to your WordPress site using WP Fusion. Using these webhooks, you can create new users on your WordPress site, or update existing users’ meta data and tags.
Webhooks are managed in Customerly by going to Settings >> Webhooks. You can create a new webhook and then specify which events should trigger it.
In the example above we have the webhook set to update the WordPress user whenever the contact is tagged or their details are updated in Customerly. For the structure of the webhook URL see the examples below:
#To update a user’s tags
To update an existing WordPress user’s tags from the contact record, the URL for the webhook should look like the following:
#To update a user’s tags and meta data
To update a user’s tags and pull any new meta data from Customerly for that contact, the URL for the webhook should look like the following:
#Create a new user
To create a new user, use the following URL:
You can also specify additional parameters in user creation. For example, to send the user a welcome email containing a link to log in on your site, use the following:
You can also specify a specific user role to be assigned to the new user. For example, to set the new user to the “customer” role, use the following:
Note that you have to have registered a “customer” role on your site for this to work. By default users will be assigned the role of “subscriber”.
The add method will update a user if an existing user already exists. It will not create a duplicate user.
user_passon your website, the new users will be given the usernames and passwords stored in their Customerly contact record.
New user accounts will be created with an automatically generated password. If you’d like to use this password in your email marketing, you can send the password back to Customerly after it has been generated.
In the Webhooks section of the General settings tab, check the box for Return Password, and select a field in Customerly where the password should be stored.
After a new user is created, their automatically generated password will now be saved back to their contact record, and you can use a merge field to include it in an email. The username will be the contact’s email address.