CRM Webhook Action to *PULL* User Meta from WP Site
I know there’s the option to set up a Webhook Flow Action in the CRM (in my client’s particular case it’s Klaviyo) and then push the profile’s lists and meta back to the website but it would be ideal to also be able to *pull* the website data into the CRM via a webhook triggered by the CRM — either all meta or even better a WP user meta field that could be specified in the webhook URL or data. We’ve already set up some WPF watch fields but in certain cases the WP profile meta fields are populated at checkout which could be a few seconds before the WP profile is created, linked to the CRM profile and then runs through the initial sync so for new orders/customers the watch field “action” seems to run too early and therefore doesn’t push the user’s meta data to the CRM. If there was a webhook action to not only push the user’s meta and lists from the CRM but also to pull the data we could have conditional logic in the CRM (Klaviyo) flow checking whether the data exists on the CRM profile, and if not we trigger the webhook to pull the data from the WP profile. We already had a support case open about this and Ace gave some great workarounds for the time being but I still think it would be a useful addition for your plugin. 🙂
Robert Hemsing shared this idea
Sure should be straightforward enough. Queued for the next update.
Legend! This would be a game-changer for my client’s setup.
Hi Jack!
I think this feature was included in the last plugin update 3.47.12 on 8th May, wasn’t it? I can’t seem to find any documentation about the “push” webhook action on your site. Any chance you could point me in the right direction if I just can’t find it, or add it if it’s not there yet?
Hey Robert! Yep, you spotted it — shipped in v3.47.12. Thanks for the docs nudge, hadn’t gotten around to updating them yet. Just added the full push action documentation here: https://wpfusion.com/documentation/webhooks/about-webhooks/#push-added-in-v3-47-12
The short version: ?wpf_action=push&access_key=KEY&contact_id=123 — and you can optionally pass a fields parameter to limit which fields get pushed if you don’t need everything. Should be exactly what you need for that Klaviyo conditional flow. Let us know how it goes!
Fantastic! Thank you so much. I got the URL right except for the contact_id part. 😉
Thanks again for implementing this so quickly — this is a life-changer for my client.
Actually slight problem—Klaviyo doesn’t allow dynamic variables like {{ person|lookup:”[property key holding WP user ID” }} (in case contact_id refers to the WP User ID) or {{ person.KlaviyoID }} (in case contact_id refers to the Klaviyo profile ID) in webhook URLs.
Can the contact ID be passed on in the webhook Headers or in the JSON body instead?
I’m not sure if the same restriction exists for other CRMs as well or if it’s unique to Klaviyo that the Destination URL has to be static without dynamic values…