I’m trying to set up an automated workflow using Zapier that connects to my WordPress website. The goal is to automatically generate new posts from RSS feed content and fill in specific custom fields with data from those feeds.
The basic functionality is working fine - I can successfully create new posts in my custom post type through Zapier. However, I’m running into an issue where Zapier doesn’t recognize or display any of the custom fields I’ve set up for that particular post type.
Has anyone found a solution for making Zapier recognize custom fields? Or is there an alternative method to automatically populate these fields during the post creation process?
For context, my custom post type was built using Custom Post Type UI plugin, and the custom fields were created with ACF Pro. Any suggestions would be greatly appreciated!
Honestly, just switch to Make.com instead of Zapier. Zapier’s terrible with ACF fields - doesn’t matter what you try. Make actually handles WordPress custom fields properly and has way better support overall.
Had this exact same issue about six months ago when I was pulling content from an external API. ACF stores data using custom meta keys that Zapier’s interface can’t read properly half the time. Two things that actually worked for me: Skip Zapier’s standard WordPress action entirely. Use their Code step instead and make direct API calls to WordPress REST API. You’ll need to format the ACF data as meta fields in your POST request, but at least it works. Install WP Webhooks plugin on your WordPress site. This was a game-changer - it creates custom endpoints made specifically for automation tools and handles ACF mapping way better than Zapier’s native integration. You can map RSS data directly to ACF field names without all the guesswork. Second option needs more technical setup but it’ll save you from these annoying field recognition problems.
Been there, done that with content syndication for multiple clients. Everyone’s suggesting workarounds, but you’re basically fighting Zapier’s core limitations.
Zapier treats ACF fields like regular meta fields, but ACF’s storage structure doesn’t mesh well with external tools. Sure, you can manually map field keys, but maintaining that becomes a nightmare when you add fields or change your setup.
I ditched Zapier for Latenode after hitting this wall on three projects. Latenode gives you visual workflow blocks but with direct API control. You can structure ACF data exactly how WordPress expects it.
Here’s the flow: RSS trigger → data transformation to clean content → WordPress API block with proper ACF mapping. Add conditional logic to populate different fields based on content type or RSS source.
Best part? You see exactly what data moves between each step. No more guessing why fields won’t populate or dealing with Zapier’s black box.
Takes 15 minutes to rebuild your Zapier workflow, but it actually works consistently.
This occurs because ACF manages field data differently compared to what Zapier transmits. I faced a similar challenge with product imports recently. The solution involved creating a custom function in functions.php that serves as a translator. This function hooks into post creation and automatically maps the incoming data to ACF fields. You can send regular post meta through Zapier with generic field names, allowing your function to catch these and convert them into the correct ACF format using update_field(). This method is more manageable than dealing with Zapier’s cumbersome interface. Once configured, it operates seamlessly without requiring additional plugins or switching platforms.
Your problem is ACF storing field data in a way Zapier can’t read properly. I hit this same issue last year working on automated content workflows for news sites. Quickest fix: Go into your ACF field group settings and turn on “Show in REST API” for each group. But that won’t solve everything - Zapier still needs the right endpoint structure. What actually worked for me was the ACF to REST API plugin. It creates proper REST endpoints for your custom fields. Install it, then refresh your Zapier WordPress connection. Your ACF fields should show up in the dropdown when you’re setting up actions. The plugin handles field mapping automatically and keeps data types intact. One more thing - make sure your custom post type has REST API support enabled in Custom Post Type UI settings. Without it, Zapier won’t see your posts at all. This keeps everything in your current workflow without needing custom code or switching platforms.
acf pro lets you expose fields to the rest api right in the field group settings. turn that on and zapier will grab them automatically - no messing with field keys. this fixed it for my client sites when everything else failed.
ACF fields don’t show up in Zapier because they’re stored as WordPress meta fields with weird naming that Zapier can’t handle properly. I hit this same issue when automating event posts from a calendar feed. Here’s what worked: use Zapier’s Custom Fields option in the WordPress action and manually add each field with the exact ACF field key - not the field name you see in the interface. The field key looks like field_5f8a9b2c1d3e4 and you’ll find it in your ACF field settings. Just add custom fields in Zapier using these keys as field names. Takes forever to set up but works great once it’s done. You can grab the field keys by editing each field in ACF or checking the field group export. This way you stay in Zapier without messing with code or extra plugins.
Been there, done that. Zapier’s WordPress integration sucks for custom fields, especially ACF ones.
What you’re hitting is super common. Zapier treats ACF fields as meta fields, but they don’t show up right in the interface. When they do appear, the mapping’s all over the place.
I fought this same battle until I ditched Zapier for WordPress stuff. Now I use Latenode instead - it handles custom fields way better since you work directly with WordPress REST API and control the field mapping yourself.
With Latenode, set up your RSS trigger, process the content, then use proper API calls to create posts with all ACF fields populated correctly. No more guessing which fields appear or dealing with weird formatting.
Setup takes 10 minutes and you get actual control over data transformation. Plus you can add logic for image processing, content cleanup, or conditional field population.