Hi, I have configured the integration between zapier and Paid Memberships Pro to create a user, but when I try the zap I get this error “The app returned” Forbidden “” how can I fix it?

I have been working with this for hours and am 2000% sure that I have followed everything to a T on all documentations, YouTube Videos, Etc but I keep receiving this error when I try to connect a zap to PMPro

“The app returned “A valid API key is required.”. It looks like your connected account doesn’t have permission to complete this step. You should contact the administrator for your account and make sure you have the needed permissions. We made a request to membership.shesblogging.co and received (403) Forbidden.”

Please help! It’s driving me insane!

Hi there

as stated, it seems that, PMPro Zapier add-on is submitting duplicate data for successful paid orders that involve PayPal Express.. it does NOT happen with Stripe.

I understand that Zapier add-on doesn’t see much LOVE from PMPro team/authors however I’d totally appreciate if you can help iron out the issue. Duplicate incoming data results in duplicate runs of Zapier scenarios and that’s a huge issue.

thanks

Hi there

I use PMPro as well as Zapier and Cancellation reason add-ons. However, when a user changes membership level (i.e. Cancellation) then Zapier add-on “membership changes” webhook fires as expected with the user information such as WP userid, email and membership status. However, I notice that “Cancellation reason” or $reason variable is never passed onto Zapier change-membership webhook as a result Zapier never receives the cancellation reason.

I think it should be trivial to pass $reason to Zapier webhook so that the reason comes through along with other meta data in the incoming webhook (to Zapier).

Truly appreciate if you can add that to Zapier add-on.

Thanks

Hi there

Is it possible to de-dupe the HTTP POSTs when they are identical and issues within a reasonably small time window.. I have seen duplicate HTTP POSTS happening so thought it would be worth looking to also Denial of Service proof the code.. I have seen a situation where a user with one unique emails can sign up for a Free plan as many times as he wants (either actually checking out repeatedly or refreshing it multiple times .. not sure..).. but while the fix should be on PMPro side to avoid Order DoS, I think it would be wise to also protect Zapier add-on to not be used as DoS amplification surface.

thanks

Hi there

Please add necessary user metadata (email should be mandatory) so that email marketing platform and so on so forth can actually make use of this data for follow up. As-is, there is no way to reconcile the following data with the original order or the origin at all.

Please help!

Using latest PMPro, Zapier and Cancellation reason plugin versions.
order__certificate_id 0
order__user_id 0
order__affiliate_id
order__status
order__timestamp 1570078200
order__billing__street
order__code 6EFBF2B093
order__cardtype
order__subtotal 0
order__checkout_id 69
order__billing__name
order__Email
order__billing__state
order__payment_type
username
order__billing__zip
order__Address1
order__total 0
order__expirationyear
order__gateway_environment live
order__expirationmonth
order__notes
Reason for cancelling:
order__subscription_transaction_id
order__payment_transaction_id
order__FirstName
order__certificateamount
order__affiliate_subid
order__membership_id 0
order__billing__country
order__accountnumber
order__billing__city
order__couponamount
order__id 71
order__LastName
order__billing__phone
order__gateway stripe
order__tax 0

HI there

Is there any way to add two Zapier Catch Hooks (= two different web hooks URLs) for new order, update order or change membership level action triggers?

New Order Trigger > POST to Webhook #1
New Order Trigger > POST to Webhook #2

I’d like to catch each PMPro trigger into two different web hooks for two different apps.

Thanks

Hi, this plugin is working fine except for one scenario. We have a “free” membership level, in which case there isn’t any billing information collected. While the first and last name is still collected on the website, that information doesn’t appear to be available in the add_order action for this plugin.

Thus, when we have a new membership at the free level, our Zap can’t see the first and last name data, which makes it fail, as it’s trying to do a lookup in the resulting application (QuickBooks Online) but chokes when there isn’t a value for name.

I can’t seem to find a way around this, and it seems like the first and last names should be included in the action data. Am I missing anything? If not, would you be able to update the plugin so it includes this information?

Thanks.

Hi there,

Pre sales question!

We would like to use the PMPro membership plugin, however, does this addon create new user in WordPress as an action should the user not be found? Or does it just updates existing users and adds them as members etc..?

Thanks