標籤： webhooks-zapier

Zapier Guide

#Overview
Using this addon with Zapier allows you to trigger Zaps when users register on your site, update their profile, or when a tag is applied or removed.
For an example we』ll set up a workflow that triggers an on-site message in Intercom when someone completes a course.
#Setup
Navigate to Settings » WP Fusion and click on the webhooks tab to access the webhooks list. Click 「Add New」 to create a new webhook.

For the trigger select Tags Applied, and in the tag selection box select the tag that will be applied when the course is completed. For the Post Fields you』ll want to enable at least user_email so the user can be identified in Intercom.
Then head over to Zapier and create a new Zap. For the trigger select Webhooks.

For the trigger type, select Catch Hook, and click Save + Continue.

Zapier will give you a unique URL to use for your webhook. Copy this URL into the Delivery URL field in the webhook settings, and click the Send Test button. Then switch back to Zapier and click 「Ok, I did this」.
On the next page you should see your incoming webhook listed, and you can expand it to see all of the data that was captured. If everything looks right, proceed to the next step.
#Actions
Now that the data is set up to be captured, you can use that data in any Zapier action. Here we』ve created a 「Incoming Message」 action in Intercom, which uses the data from the webhook to target the user and personalize the message.

You can use the 「Insert A Field」 button to insert any dynamic data from the webhook.

Above is another example, sending a direct message in Slack when a webhook has been received. If you use Slack to support your membership community you could use this to automatically congratulate members in a Slack channel when they reach goals on your website.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

ActiveCampaign Webhooks

#Overview
You can use webhooks in ActiveCampaign to send data back to your WordPress site using WP Fusion. Using webhooks you can create new users on your WordPress site based on automations in ActiveCampaign, or update existing users』 meta data and tags.
Note: As of March 2021, SiteGround』s anti-bot captcha system automatically blocks all incoming ActiveCampaign webhooks. If webhooks aren』t working on SiteGround, contact SiteGround support and ask for the bot protection to be turned off for your account.
Having trouble receiving webhooks? Check out our troubleshooting guide.
There are two ways to manage webhooks in ActiveCampaign, either via an Automation or in the Developer Settings.
#Automation Method
(Recommended) The automation method is best if you need to send a webhook to create or update a WordPress user as part of a specific process. For example:

Tag 「Website Access」 is added
Send webhook to create WordPress user
Send welcome email
Wait 3 days
Apply tag 「Unlock Course Two」
Send webhook to update tags

Using a webhook in an automation lets you easily visualize the entire automation flow, and see where individual contacts are in the process.

You』ll also be able to visualize where a single contact is in the automation, when the webhook was sent, and whether or not it was received successfully. Using webhooks in automations gives you a lot more control and better reporting than using Global Webhooks (see below).
To use webhooks in automations first create an automation and add a webhook to it, like in the example above. You have three options for the webhook, update, update_tags and add (explained below). For each you will need to supply your access key, which can be obtained from the main panel in your WP Fusion settings.

When the contact reaches the webhook step in the automation ActiveCampain will notify WP Fusion to load the contact』s data from ActiveCampaign.
#A note on 「failed」 webhooks
When viewing automation reports you may see your webhooks being marked as 「failed」 by ActiveCampaign, like in the screenshot below.

This does not necessarily mean that the webhook failed. ActiveCampaign will mark any webhook as failed if your server takes longer than 5 seconds to respond.
Since there』s a fair deal of processing involved in receiving a webhook (see some average timings here), it』s not uncommon for your server to take longer than 5 seconds, especially with shared hosting.
For a definitive answer as to whether the webhook was processed, you can check the WP Fusion logs.
If you』d prefer not to see the Failed symbol in the automation reports, you can also set your webhooks to run asynchronously.
This does not speed up the time required to process the webhook, or make webhooks more reliable, it just means that WP Fusion will immediately respond to ActiveCampaign that every webhook was successful, and then actually process the webhook a few seconds later.
#Developer Settings Method
(Advanced) You can also set up webhooks which are global to your account. This is best if you』re manually editing contact records in ActiveCampaign (outside of an automation) and need these changes synced to WordPress.
Note: It』s not recommended to set up global webhooks with the add method, as then every contact in ActiveCampaign will be given a WordPress user account.
To set up a webhook navigate to Developer » Webhooks in your ActiveCampaign admin settings, and click Add to create a new webhook.

Under Type select the events that should trigger the webhook.

For Initialize From, select which types of events should trigger the webhook. ActiveCampaign has a description of the types here.
You shouldn』t enable By the API as this will send a webhook after WP Fusion sends an API call to apply a tag, which is redundant.
Note that, despite the descriptions in the ActiveCampaign help portal, we have tested and found that tags applied in automations will trigger a global webhook if it is set to By an admin user. If you』re experiencing unexpected webhooks or a high volume of webhooks, it』s recommended to disable that trigger.
Help us our by voting on this feature request with ActiveCampaign to create a webhook trigger specific to manual contact edits.
Keep in mind that, because these webhooks are global to your ActiveCampaign account, bulk editing contacts will trigger webhooks to be sent to your site for every edited contact, which may make your WordPress site temporarily unstable.
Note: If you』ve set up global webhooks with the update or update_tags method it』s not necessary to also include those same webhooks in automations.
#Webhook URL parameters
You can format your webhook URL in a few different ways to customize the behavior:
#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 ActiveCampaign for that contact, the URL for the webhook should look like the following:
http://mydomain.com/?wpf_action=update&access_key=YOURACCESSKEY
#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 your ActiveCampaign application, 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 ActiveCampaign contact record.
#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 ActiveCampaign 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 ActiveCampaign 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.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

Agile CRM Webhooks

#Overview
You can use webhooks in Agile CRM to send data back to your WordPress site using WP Fusion. Using webhooks you can create new users on your WordPress site based on rules in Agile CRM, or update existing users』 meta data and tags.
There are two ways to sync data between AgileCRM and WP Fusion. Method One is available on all plans. Method Two is available with Enterprise plans, but not the lower pricing tiers.
Having trouble receiving webhooks? Check out our troubleshooting guide.
#Method One
In a new or existing campaign, add a JSON IO item to any campaign. This could be triggered by a tag being applied, or part of a larger sequence.

Click on the JSON IO item and in the window that pops up, configure the parameters like in the screenshot below. Replace the URL field with the URL to the home page of your site, and put your access key (from the main page of the WP Fusion settings) in the access_key field.

 
#Method Two
Agile CRM also supports an alternate method of sending webhooks that doesn』t require setting up a campaign sequence. Using this method, WP Fusion will pull the latest data from Agile CRM any time a contact』s details are updated, or a tag is added/removed. For more information on this method, see Agile CRM』s documentation.
To use this method with WP Fusion, create a new webhook and set the URL following the example below.

The URL should be in the format:
http://yourwebsite.com/?wpf_action=update&access_key=YOURACCESSKEY
Make sure to select 「Contact」 as the module, and replace ACCESSKEY in the URL with your unique access key (visible on the WP Fusion settings page). Once the webhook is enabled, any changes to contacts in Agile CRM will be reflected on your site immediately.
 
#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 AgileCRM for that contact, the URL for the webhook should look like the following:
http://mydomain.com/?wpf_action=update&access_key=YOURACCESSKEY
 
#Create a new user
To create a new user, set wpf_action to add.
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, add a parameter send_notification and set it to true.
You can also specify a specific user role to be assigned to the new user, by adding a role parameter. For example, to set the new user to the 「customer」 role, set role to 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.
 
#Update an existing record only.
If you only want to update an existing contact record to pull any new data from Agile CRM for that contact but NOT create a new user in WordPress, set wpf_action to update.
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 your Agile CRM application, 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 Agile CRM contact record.
#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 Infusionsoft 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 Agile CRM 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.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

Autonami Webhooks

#Overview
With Autonami Pro, you can use webhooks in automations to connect to WP Fusion installed on another site.
Using webhooks you can import new users on your WordPress site based on rules in Autonami, or update existing users』 meta data and tags.
For example, you could sell access to a course using WooCommerce and Autonami on Site A, and using a webhook, WP Fusion on Site B can automatically import the new customer and enroll them in the course they purchased.
Having trouble receiving webhooks? Check out our troubleshooting guide.
#Setup
Navigate to Autonami » Automations and create a new automation to handle the webhook. Select a trigger (such as a tag being applied), and click the Add Direct Action button to add a new action.

In the popup that appears, select Send Data, and then HTTP Request.
In the webhook settings, configure the webhook like in the screenshot below.

The settings should be:

Enter URL: This is the URL to the website where WP Fusion is installed.
Method: Either GET or POST, but sometimes POST requests get blocked by security plugins, so we recommend GET.
Data: At minimum you must have:

contact_id: {{ contact_id }} (this tells WP Fusion which contact to import)
access_key: (the access key from the bottom of the General tab in the WP Fusion settings)
wpf_action: (see below for options)

#Webhook parameters
You can format your webhook parameters in a few different ways to customize the behavior. For each you will need to supply your access key, which can be obtained from the bottom of the main settings panel in your WP Fusion settings.
#To update a user』s tags
To update an existing WordPress user』s tags from the contact record, the data parameters should be
contact_id = {{ contact_id }}
wpf_action = update_tags
access_key = [your access key]
#To update a user』s tags and meta data
To update a user』s tags and pull any new meta data from Autonami for that contact, the data parameters for the webhook should look like the following:
contact_id = {{ contact_id }}
wpf_action = update
access_key = [your access key]
#Create a new user
To create a new user, use the following:
contact_id = {{ contact_id }}
wpf_action = add
access_key = [your access key]
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:
contact_id = {{ contact_id }}
wpf_action = update_tags
access_key = [your access key]
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:
contact_id = {{ contact_id }}
wpf_action = update_tags
access_key = [your access key]
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 Autonami, 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 Autonami contact record.
#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 Autonami 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 Autonami 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.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No