Supported custom field plugins ability reference

What Custom fields (any plugin) needs before these load

At least one of ACF, Meta Box, Pods, JetEngine, ACPT or ASE Pro has to be active, with its own GoBuildWP Pro module loaded. With none of them the call returns wppilot_fields_no_provider. With two or more it refuses to choose and returns wppilot_fields_provider_ambiguous until provider is passed, because the same meta key can be read by two plugins and a guess would write to the wrong one. Each post is also checked against the edit_post capability of the connected user.

Custom fields (any plugin) editions

free, pro

Agent skills shipped

acf-integration, metabox-integration, pods-integration, jetengine-integration, acpt-integration, ase-integration

Plan first, then confirm

A call without dry_run and without confirm is refused with wppilot_confirmation_required (HTTP 409) and a message that states how many posts would be overwritten and through which plugin, and tells the agent to show the plan to the user first. dry_run=true reads each post's current values and returns them beside the planned ones without writing; for ACF the read is unformatted, so the comparison is between stored values rather than what a template would display. The summary counts planned, updated, partial and error results.

Up to 100 posts go in one call, either as post_ids sharing the same values or as items that each carry their own. When both are given, per-item values win key by key.

How each plugin is written

ACF values go through update_field, and repeater, flexible content, group, gallery and clone fields need the same {value, mode: "replace"} wrapper that wppilot/acf-write-values asks for, because writing them replaces the whole previous value. Meta Box uses rwmb_set_meta, Pods save_pod_item, ASE Pro update_cf, and ACPT save_acpt_meta_field_value with fields addressed as box_name.field_name. JetEngine values are written as post meta, but only for field names a JetEngine meta box or post type declares for that post type.

What can and cannot be undone

Every written post gets its own change-ledger row, which wppilot/rollback-change restores. Two cases are recorded as irreversible instead, with the reason in the result: Pods post types that keep their fields in their own table rather than post meta, and Meta Box writes while MB Custom Table is active, since both put the value where a post snapshot cannot reach it.

Representative call sequence

This sequence describes the documented calls and checks to perform. It is not a recorded result from an installed WordPress site. Inspect returned errors and partial results, then verify the saved values and affected output before proceeding.

Set an end date on 30 event posts whose fields are defined in Meta Box, on a site that also runs ACF.

1. 01 wppilot/metabox-read-values Reads the field on one event first, to confirm the field id and the date format Meta Box stores.
2. 02 wppilot/fields-bulk-update-values Called with provider set to metabox and dry_run=true: returns each event's current and planned date. Without provider the call would stop, since ACF is active too.
3. 03 wppilot/fields-bulk-update-values Called again with confirm=true after the plan is approved; one ledger row per event, recorded as irreversible when custom-table values cannot be snapshotted, with an explicit reason. Inspect every per-item result.

Questions about Custom fields (any plugin)