Drip Webhooks

Overview

You can use HTTP Posts and Webhooks in Drip to send data back to your WordPress site when a contact’s profile has been modified, or tags have been added or removed. You can also automatically generate new WordPress user accounts for Drip subscribers.

Having trouble receiving webhooks? Check out our troubleshooting guide.

HTTP Posts

Using an HTTP Post in Drip allows you to send data back to WordPress as part of an Automation, or via a Rule based trigger. You can set this up by navigating to the Automation tab in Drip. To create a rule-based trigger, head to the Rules tab and create a new rule.

First set the criteria which will trigger the rule. In this case, we’re telling Drip to send the HTTP Post whenever the tag “Create WordPress User” is applied to a subscriber.

In the second panel, select “Send an HTTP post” from the dropdown. For the Endpoint URL, enter the URL to your site. In this example, we’re triggering the creation of a new WordPress user when the tag is applied. This is achieved by using wpf_action=add in the URL. You also need to supply your access key, which can be found from the WP Fusion settings page on your site.

Depending on the action you’re trying to perform, there are several additional parameters you can include in the URL:

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:

http://mydomain.com/?wpf_action=update_tags&access_key=YOURACCESSKEY

To update a user’s tags and meta data

To update a user’s tags and pull any new meta data from Drip for that contact, the URL for the webhook should look like the following:

http://mydomain.com/?wpf_action=update&access_key=YOURACCESSKEY

To create a new user

To create a new user, use the following URL:

http://mydomain.com/?wpf_action=add&access_key=YOURACCESSKEY

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:

http://mydomain.com/?wpf_action=add&access_key=YOURACCESSKEY&send_notification=true

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:

http://mydomain.com/?wpf_action=add&access_key=YOURACCESSKEY&role=customer

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.

Note: By default, user accounts will be created with their email address as the username and a randomly generated password. However, if you have created a custom username field and password field in Drip, and enabled these fields in WP Fusion for sync with user_login and user_pass on your website, the new users will be given the usernames and passwords stored in their Drip subscriber record.

HTTP Posts in Automations

You can also trigger an HTTP Post as part of an automation. Add a new node to the automation and follow the same steps outlined above.

User passwords

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 Drip 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 Drip 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.