How to configure Patreon membership levels with Zapier integration for WordPress PMPro

I need help setting up a workflow that connects Patreon subscription tiers with Paid Memberships Pro on my WordPress site using Zapier as the bridge.

I’m working on automating the process where when someone subscribes to a specific tier on Patreon, it automatically creates or updates their membership level in PMPro through Zapier. I’ve been following the configuration steps but I’m stuck at a particular point in the setup process.

The main challenge is mapping the Patreon tier data correctly so that it creates the appropriate membership level in PMPro. The standard documentation doesn’t seem to cover this specific use case of pulling membership data from Patreon and pushing it to PMPro.

Has anyone successfully set up this kind of integration before? What field mappings should I use to ensure the membership levels sync properly between these platforms?

the PMPro Zapier connector is buggy with patreon data. I used zapier’s code step to manually parse the patreon webhook payload instead. grab the pledge amount and user email, then use if/else logic to assign the correct membership level ID. test with real patreon webhooks - dont use zapier’s sample data. thats where most ppl screw up.

Skip Zapier’s built-in PMPro actions - they’re terrible with tier mapping. I use PMPro’s REST API endpoints instead. Way better control. Set up a webhook in Zapier that sends POST requests straight to PMPro’s user registration endpoint. You’ll need to enable PMPro’s REST API and grab your API keys first. For mapping tiers, pull the Patreon tier amount or title from your trigger data. Then use Zapier’s conditional logic to match it with the right PMPro membership level ID. One gotcha - handle existing users differently. New signups go through user creation, but existing users need the membership update endpoint instead. This setup gives you way more control over data flow and error handling than the native integration.

Had the same problems setting this up. The game-changer was ditching the default mappings and creating custom ones in Zapier’s action step instead. You’ve got to map the Patreon tier ID or name to a custom field first - that’s how you match it to the right PMPro membership level ID. I used Zapier’s Formatter to build a lookup table that converts Patreon tier names to PMPro level numbers. Works way better. Also, set up a separate zap for cancellations and downgrades since they need different handling. Pro tip: webhooks work better than the standard Patreon trigger, especially if you’ve got multiple tiers.