Hi,

At the moment, if a member pays for their membership by credit card, almost no data gets imported to zapier. See below image what gets imported. If they pay by check/bank transfer, I get all the data and can continue the zap through to my accounting software.

Regards,
Veshil

Expected Behavior:

When activating the plugin an API key should be generated. We then check if an API is present, and if it is, don't generate a new one.

Current Behavior:

When hitting 'Save' on the Zapier Settings page, the API key on the 'Receive Data From Zapier' page changes on every save.

Relates to https://www.paidmembershipspro.com/forums/topic/api-key-for-zapier-keeps-on-changing/ (Moderators Only)

We should add additional hooks before pushing data to Zapier so we can filter the data (add in or take out extra data as needed via hooks).

This solves an issue when passing data to Zapier is not taking custom fields into consideration and allows user's to pass custom data to them.

I am testing the plugin but can't seem to get the username and email address in Zapier. It always shows empty. I have real subscriptions and dummy data. None of the attempts succeeded. (I have the billing address fields not showing.)

We should add the option to send new user notifications from PMPro Zapier, or at least add a hook after the user is created.

Support Ticket (Moderators Only)
https://www.paidmembershipspro.com/forums/topic/send-user-details-when-order-is-placed-via-zapier-hook/

We should have an option to only send data when a user completes checkout and not after every membership level change.

This will help users capture initial data only if needed.

This should be fairly quick to implement from other triggers.

User would like a trigger for the event when a member cancels their membership.

Support Ticket (Moderators Only)
https://www.paidmembershipspro.com/forums/topic/cancellation-trigger-for-zapier-bug/

We should send an email when the user is created or updated.

A user requested to support MMPU Add On.

Currently, we hit the zapier webhooks right away when a new order is created or a user's membership level changes.

Especially when new orders and membership changes are happening in batch (e.g. during imports) or if there are multiple webhooks to hit (#11) we run the risk of having a timeout or just extending the load time of checkout/etc on the site.

We should queue up webhook calls and run them in the background.

A user would like to send custom fields when sending data to Zapier, we should add in filters for this.

We need better documentation for the "Receive data from Zapier (Actions)." For example, how do I use the add_member action? Does it go in the URL somewhere?

In Zapier, the First and Last Name fields are not being imported to the relevant field in Zapier, they're not coming at all. The fields that are being imported are only username, email, amount, id So right now I have a number of invoices with people's usernames on them instead of their real names and companies.

When I use this plugin with an active zap, the order page redirects to information sent to Zapier in an empty page rather than directing to the myurl.com/order-confirmation page. Zapier still successfully records the transaction, and the membership is also successfully recorded and charged, but the redirect is messed up. The missed redirect is corrected when the plugin is turned off. This issue occurs in test mode (Stripe). I have not tested in live mode.

Here is the displayed text on the missed redirect (identifying info mod'd):
{"username":"testusername","order":{"gateway":"stripe","id":"01","code":"*******74","user_id":"20","membership_id":"1","billing":{"name":"","street":"","city":"","state":"","zip":"","country":"","phone":""},"FirstName":"","LastName":"","Address1":"","Email":"[email protected]","subtotal":"19.99","tax":"0","couponamount":"","certificate_id":"0","certificateamount":"","total":"19.99","payment_type":"","cardtype":"Visa","accountnumber":"XXXXXXXXXXXX4242","expirationmonth":"06","expirationyear":"2018","status":"success","gateway_environment":"sandbox","payment_transaction_id":"*****************UC9","subscription_transaction_id":"*******************8p3","timestamp":"1521797358","affiliate_id":"","affiliate_subid":"","notes":"","checkout_id":"14"}}

Any help appreciated.

The user ID value is 0 when checking out for the first time with Stripe.

Steps to recreate:

1. Enable "New Order" for send data to Zapier step.
2. You can enter any URL, if you are var_dumping or enter your Zapier URL.
3. Set your payment gateway as Stripe.
4. Logout and do a first time checkout.

The user ID will be 0, causing other data to be empty.

We should look at running code on 'pmpro_after_checkout'.

This will only run when a user signs up and might be useful.

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

The order object stores the date as a timestamp, we should look at adjusting this with formatting to make it human-readable.

In PMPro v2.9, the MemberOrder class was refactored to avoid warnings in PHP 8+. Part of this refactor was defining private properties for the class which can be accessed using a magic getter.

PMPro Zapier sends information about the MemberOrder by adding the entire order to the webhook request ( $data['order'] = $order;). The fact that order properties are now private is causing this approach to no longer work. Instead, we should change PMPro Zapier to send specific pieces of order information in the webhook request and use the magic getter to retrieve that information. This also has the added benefit of standardizing the order information that Zapier can expect to receive.

We should pass the user_id value when the add_member is created and the user's level is changed for our webhook handler here.

Code Ref:

When cancelling a level, the 'membership level changed' trigger sets level->id to "0". But we unset level->id if changing to another (non-zero) level, sending level->ID instead (capitalized).

Forum thread (mods only): https://www.paidmembershipspro.com/forums/topic/zapier-integration-with-activecampaign/

When data is constructed in class-pmpro-zapier.php from the MemberOrder object, the discount code is not properly added to the $data array that is then sent to Zapier.

When the order is loaded it's handled in the code below for all of the different Zapier options available:

static function pmpro_added_order( $order ) {
		// bail if setting is not checked
		$options = PMPro_Zapier::get_options();
		if ( empty( $options['pmpro_added_order'] ) ) {
			return;
		}

		// Get the saved order.
		$order = new MemberOrder( $order->id );

But this code loads in the DiscountCode object into $order, which is then set to NULL when passed through to Zapier.

The additional of this line will retrieve the discount code used and replace the discount_code object:

$order->discount_code = $order->getDiscountCode()->code;

This will then be available from Zapier to assign to the target application.

• When cancelling a membership level by using the change membership level webhook option, we would typically set it to 0 to remove the level
• Currently, when doing so, we get the error "You must pass in valid level_id."
• We check for a string on https://github.com/strangerstudios/pmpro-zapier/blob/master/includes/webhook-handler.php#L102 where the $level_id is not an int. Changing that check seems to resolve the issue.

Relates to https://www.paidmembershipspro.com/forums/topic/api-key-for-zapier-keeps-on-changing/ (mods only)

A request has come in to store some additional fields as user meta.

We see people using the Add On when they should rather be using the native App. That brought up the idea that we could use this Add On as a place to embed the full Zapier experience / native app features as well as the current webhook-based functionality.

We'll need some UI help to show that there are two ways to use this Add On: use the Zapier App natively or use the webhook method.

We currently have around 1,000+ people using this plugin. Whereas our Zapier App has far fewer. This could be because people are just confused about what's needed.

I believe it will make things less confusing if we show that you don't need to set this all up via Webhooks and can instead use the Zap builder interface to create automations with PMPro.

This comes up quite often as users assume that once they use the Add Name to Checkout Add-on that the fields would automatically sent through to Zapier. Perhaps we can add those fields in be default and if the plugin isn't in use, the values just return empty.

You might want to update multiple zaps/etc when a new order is created or user changes membership level. We should add a way to add multiple webhooks to this page, store them in an array, and hit all of the webhooks when something happens.

Of course this greatly increases the chance of a timeout when hitting the webhooks, so we should consider queuing up the webhook calls to be run in the background.

Instead of using a URL like /?pmpro_zapier_webhook=1&api_key=...

We should use the WP REST API. We can create an route /pmpro_zapier/v1/ and then add endpoints for members and orders.

So URLs would look like:

/pmpro_zapier/v1/orders/add/?code=...&api_key=...
/pmpro_zapier/v1/orders/{order_id}/update/?code=&api_key=...
/pmpro_zapier/v1/members/add/?user_email=...&level_id=...&api_key=...
/pmpro_zapier/v1/members/{user_id or user_email or user_login}/change_membership_level/...
/pmpro_zapier/v1/members/{user_id or user_email or user_login}/has_membership/...

This would basically mirror the REST API for PMPro in general. You could actually use the PMPro REST API instead, but I think it's a good idea to copy it in this plugin as well to make it easier for people to setup/etc.

We should look into adding more trigger locations, some are but not limited to:

• Integrate with PMPro Approval actions such as member approved, denied, reset.
• After checkout (one time triggers)

Please feel free to comment with new triggers you may like to see added

I think to solve this, we could strategically place filters that will allow devs/users to only send a notification to Zapier if a condition is met (i.e. certain level checkout etc).

This will help with more flexibility.

Suggestion comes from this ticket https://www.paidmembershipspro.com/forums/topic/changing-custom-fields-using-zapier/

Adding a hook within each event in the webhook handler would help to allow you to send custom field data from Zapier and store it to user meta.

Example: A Google Sheet has a custom field called 'Height' and this can then be hooked into the webhook handler to add the 'height' field to the user meta too when it's being updated or added.

As per this topic: https://www.paidmembershipspro.com/forums/topic/zapier-pmpro/

It would be nice to have a few extra filters in places such as https://github.com/strangerstudios/pmpro-zapier/blob/master/includes/class-pmpro-zapier.php#L257 in the prepare_request method as well as on https://github.com/strangerstudios/pmpro-zapier/blob/master/includes/class-pmpro-zapier.php#L269 in the post method.

This is similar to Issue #11 however in the case of the above topic, they'd need to have a different hook for each membership level purchased.

Would also work out for a great code recipe if filters are in place.

This Add On needs to be localized.

When we prepare a Zapier request here: https://github.com/strangerstudios/pmpro-zapier/blob/master/includes/class-pmpro-zapier.php#L93-L95

I assumed the request type we send into the API is available on the Zapier end if you wanted to filter different types of requests. We should maybe pass a value "trigger" with the name of the PMPro hook that triggered the zap.

When you add a level to a user using pmpro_changeMembershipLevel function it does not add in the expiration date etc.

We should build this in by default, it should add in the current level settings when assigning the level to the user.