Advanced Custom Fields (ACF)

How to use Whalesync's WordPress connector with ACF

Whalesync supports syncing Custom Post Types and Custom Fields with ACF.

Using ACF Custom Fields

To use ACF Custom Fields, you'll need to toggle the setting "show in REST API" on for each Field Group you want to use:

Because of how Wordpress returns metadata for ACF fields through the API, you also need to have at least one rule in the "Location Rules" that checks for the Post Types you want the field to be a part of. For example, if you want to sync your ACF fields with the Posts table, you'll need a check for "Post Type is equal to Post".

If you use more complex logic than this already, and don't want to always show the ACF fields in a group on a specific table, you can add a condition that will never match along with the check in a new rule group. This will still allow Whalesync to pick up the field, but won't affect how your fields are shown in the Wordpress UI.

Image Fields

In order to sync an image into an ACF field, the ACF field needs to be of Text or URL. Whalesync will sync an image URL into the field when you upload an image on the other side of the sync (e.g. in an Airtable Attachment field). To display this correctly, your Wordpress template will need to retrieve the image as a URL, and not an image reference or array:

<img src="<?php the_field('my_acf_image_field_name'); ?>">

Supported Field Types

Field
Status

👤 Text

✅ Supported

🔽 Text Area

✅ Supported

☑️ Number

✅ Supported

🗃️ Range

✅ Supported

✉️ Email

✅ Supported

📂 URL

✅ Supported

🖼️ Password

✅ Supported

🖼️ Image

🔜 Coming Soon

👤 Author

✅ Supported

Last updated

Was this helpful?