This post is part of an ongoing series. More ways to use Stripe and Zapier together are coming soon.
Making the Zap
This can be done fairly easily without code using one of the Zapier’s email newsletter or drip email zaps. This also works whether or not you’re using WP Simple Pay (as long as you’re using Stripe). Let’s walk through how to accomplish this.
Once you’re logged into Zapier, connect your Stripe account within Zapier if you haven’t already. Make sure to connect both your Test and Live accounts.
Next, simply search for your mailing list provider in the Zapbook and follow the instructions to connect it. In this example, we’ll connect a MailChimp account. But it should be almost the same process to set up any other mailing list provider.
You could use the pre-built Zap for adding Stripe customers to a MailChimp list, but when using WP Simple Pay, it’s better to look for Stripe charges. The primary reason is that Stripe customers are sometimes created even if the charge itself fails.
After your Stripe and mailing list accounts are connected, click Make a Zap at the top. In the Zap editor, start by naming your Zap.
To set up the Trigger, select the Stripe app, the New Charge trigger, then your Test Stripe account.
Next, below the Stripe trigger you’ve created, add a MailChimp action. Then select Add/Update Subscriber and connect your MailChimp account and list.
At this point, you’ll map Stripe charge fields to MailChimp subscriber data. Subscriber Email should be mapped to the Stripe charge Cust Email field. It should be fairly straight forward if you already fetched a test charge in the earlier step.
You can also enable Double Opt-In, Send Welcome Email, or other MailChimp settings here if needed.
Next, continue to map additional fields from the Stripe charge fields to the subscriber data. There’s even a handy search box to narrow down fields available such as “name” and “zip”. In this example, I mapped the Cust Sources Data Name to the subscriber Full Name field, and the Cust Sources Data Address Zip to the subscriber Zip Code field.
In addition, in my MailChimp list, I created a custom field titled “Skill Level”. In my WP Simple Pay Pro payment form, I added a custom drop-down field with the id of “skill_level”. Since this custom field is saved to each Stripe charge as metadata, I was able to map “Metadata Skill Level” to the custom MailChimp field “Skill Level” without a hitch. Read more about metadata and custom field values in Stripe.
After finishing the Zap you can start testing payments. As Zaps complete, simply monitor your MailChimp list to make sure it’s populating all fields properly.