Everyday workflowsLesson 9 of 15 · 6 steps

Work with custom fields

Discover an existing content model and update values through ACF or Meta Box.

Video coming soon

Your next step is ready.

Follow the complete written guide below.
The video will join it here when it’s ready.

Start the written lesson

Before you start

  • A verified connection to a practice site.
  • ACF or Meta Box active.
  • Required field-write access and plugin edition.

Let’s do this, step by step.

Step 01

Check the integration tools

Open Setup → Tools → Plugins → Dynamic Content. Choose ACF or Meta Box. Inspect dependencies and both read/write switches. Enable the actions for this task, choose Save changes, then reconnect.

Before starting, find this integration on the Tools screen. Check the required plugin and action switches. Save the changes and reconnect your app. Choose ACF or Meta Box.

Step 02

Inspect the fields

List field groups, open the target group's definition, and read current values on a test post.

Custom fields are named spaces for structured information, such as a subtitle or rating. Read their definitions before writing values.

Step 03

Choose the matching plugin route

For ACF, discover field types and nested requirements. For Meta Box, use existing field definitions only.

ACF can support more content-model operations. Meta Box's integration updates values; it does not author the field definitions.

Step 04

Update a test record

Set one existing text or number field on the exact post ID, then read it back.

Use the field's real name and accepted value. Unknown or unsupported fields need review, not a guess.

Step 05

ACF: create a model when needed

On a practice site, create an ACF-managed post type, field group, and location rule only if this is the intended task.

ACF's model tools do not delete or rename existing identifiers. Premium field types need ACF Pro, and code-registered groups remain read-only.

Step 06

ACF: import reviewed data

Have the AI extract a document locally, validate the structured rows, review the plan, and apply the unchanged batch with its plan hash.

WordPress receives the field values, not a PDF parser job. Keep the validated plan unchanged when applying it, then check every returned row.

You’re done when…

The intended fields contain valid values and are visible on the correct record.

Keep the reference handy.

The docs cover tool details and requirements for this lesson.