Pro module16 abilities

Avada ability reference

Reference for the GoBuildWP Pro 1.12.4 source. Installed schemas and policy remain authoritative.

This Avada ability reference lists every call GoBuildWP Pro registers for Avada theme options, global colours, sliders and portfolios, with the exact slug an agent sends and what the plugin's own contract says it does. Of the 16, 11 read, 4 write and 1 is marked destructive in the source.

By GoBuildWPContent updated 13 October 2026How we check claims

Read-only, write and destructive groups describe the source annotations. They do not establish a minimum safety profile, human approval or undo support. Those controls are separate: check the installed ability, the connected user and the active site policy before calling it. A read can still return sensitive data. These pages are not evidence that every operation passed an end-to-end runtime test.

What Avada needs before these load

These 16 abilities come with GoBuildWP Pro 1.12.4. Pro registration requires the Freemius SDK to permit premium code and any companion dependency the module checks to be available. The floors below apply to the named dependencies or features; an optional add-on or newer feature floor does not necessarily disable the base module. wppilot/integration-health and the module's setup call describe the installed availability.

Minimum (base): 7.15.0 WPPILOT_PRO_AVADA_MIN_VERSION
Minimum (plugin): 3.13.0 WPPILOT_PRO_FUSION_BUILDER_MIN_VERSION
Avada editions: free, pro
Agent skills shipped: avada-integration

Avada in practice

The Avada global options an agent is allowed to change

wppilot/avada-set-theme-options will not write an arbitrary key from fusion_options. The allowlist is short and grouped: seven single colours (primary, secondary, body text, link, link hover, separator and main border), three layout values (layout, site_width, main_padding), header position, layout and stickiness, footer column count and display, and five extras (lightbox, Google Maps, the to-top button on desktop and mobile, and the preloader). Any other key returns avada_unknown_setting and nothing in the request is written.

Custom CSS and every custom JavaScript slot (header, body and footer) are on a separate stop-list that is checked before the allowlist, so this module refuses to write CSS or JavaScript into those slots even if the allowlist grows later. That covers these calls only; other GoBuildWP abilities and Avada's own panel are governed separately. The palette colours and typography presets are changed with wppilot/avada-edit-global-color and wppilot/avada-edit-global-typography instead; every other Global Options panel stays in Avada's own interface.

Putting an Avada change back

Global options, a palette colour and a typography preset all live in the single fusion_options row, and the change ledger snapshots that whole option before each of those writes, so wppilot/rollback-change can restore it. A slide edit is snapshotted as a post. Slider settings are different: they are term meta on the slide-page term, which the ledger records as irreversible, so read the slider with wppilot/avada-get-slider before calling wppilot/avada-edit-slider-settings and keep the settings bag for a manual restore.

Restoring fusion_options returns the row to its earlier state as a whole. If someone changed another setting in Avada's panel after the agent's write, a rollback takes that change back too, so check the panel before restoring on a busy site.

Locks, verification and avada_write_failed

Each write takes a lock first: one for the fusion_options row, one per slide and one per slider, so two GoBuildWP writes cannot interleave a read-modify-write. Avada's own Global Options panel does not take this lock, so a person saving the panel at the same moment can still overwrite the agent's change. A lock left behind by a request that died is cleared once it is older than its time limit. After the write, GoBuildWP compares the stored row with what it meant to store. Another plugin can veto an option or meta update while WordPress still reports success, and when the stored value differs the call returns avada_write_failed naming the key. Read the value back before retrying.

The slider calls also need the Fusion Core companion plugin at its supported version. Without it they return avada_fusion_core_not_active, even though the theme options, palette and typography calls keep working.

A request to try on staging: change the primary colour to the new brand blue. The agent reads wppilot/avada-get-theme-options with include color, writes primary_color, then loads a page that uses the primary colour with the cache cleared, because Avada builds that colour into its compiled dynamic CSS.

Avada reads

Ability	What it does
`wppilot/avada-check-setup`Check Avada Setup	Reports the Avada theme environment status: theme active, version, minimum-satisfied flag, Fusion Builder companion-plugin state, Fusion Core companion-plugin state, current-user capability, `fusion_options` presence, and counts of portfolio + FAQ posts. Run this before any Avada-touching workflow to confirm the environment is ready and to detect the "theme installed but companion plugin missing" configuration.
`wppilot/avada-get-slide`Get Avada Fusion Slide	Read a single Fusion Slider slide (a `slide` post) with its full `_fusion` postmeta bag - heading + caption, media routing (image/youtube/vimeo/mp4), color overrides, per-slide link. Also returns the featured-image URL (background of the slide when `type=image`) and the slider(s) the slide is assigned to. Fields whose serialised value exceeds `max_field_bytes` are truncated and listed in `truncated_fields[]` (progressive disclosure). Set `max_field_bytes: 0` to opt out of truncation. Read-only; requires Fusion Core plugin active at min version.
`wppilot/avada-get-slider`Get Avada Fusion Slider	Read a single Fusion Slider (a `slide-page` term) with its full `_fusion` term_meta settings bag (dimensions, autoplay, animation, navigation, indicator) plus a compact list of the slides assigned to it (id, title, slug, status, modified). Use `slider` as the term slug returned by `avada-list-sliders`, or the numeric term id. Set `include_slides: false` to skip slide enumeration when only the settings are needed. Read-only; requires Fusion Core plugin active at min version.
`wppilot/avada-get-theme-options`Get Avada Theme Options	Snapshot of the `fusion_options` DB row grouped by tab (color, typography, layout, header, footer, extra). Large fields (custom CSS / custom JS) are byte-capped at `max_field_bytes` (default 20_000, opt-out with `0`) and flagged with `<field>_truncated: true`. Use `include: ["color","typography"]` to fetch a narrow subset when the caller only cares about a few tabs - progressive disclosure prevents dumping the whole option payload (~50 KB on a configured install).
`wppilot/avada-list-faqs`List Avada FAQs	Compact enumeration of `avada_faq` CPT posts. Returns rows with id, title, slug, status, modified. Paginated: default `limit=25`, hard cap 100. Use `status` to filter (default: any). This is inventory only - use `wppilot/get-content` to fetch the full content of a specific FAQ.
`wppilot/avada-list-global-colors`List Avada Global Colors	Enumerate the AWB Global Colors palette. Each row: slug (`color1`..`colorN`), label, and current color value (typically an `rgba(...)` string). Read-only. Palette storage lives in `fusion_options.color_palette`; the ability reads through `AWB_Global_Colors::get_instance()->get_palette()` so any theme filter overlaying the base palette is honoured.
`wppilot/avada-list-global-typography`List Avada Global Typography	Enumerate the AWB Global Typography presets. Each row: slug (`typography1`..`typographyN`), label, family, size, weight, lineHeight, letterSpacing, textTransform. Read-only. Preset storage lives in `fusion_options.typography_sets`; the ability reads through `AWB_Global_Typography::get_instance()->get_typography()` so any theme filter overlaying the defaults is honoured.
`wppilot/avada-list-hooks`List Avada Hooks	Curated catalogue of the ~20 most commonly used `fusion_` and `avada_` filter hooks the Avada theme exposes for customisation. Each entry reports the hook name, its category (dynamic-css, options-injection, layout, search, related-posts, other), a short description, and the number of parameters the callback receives. This is a static catalogue kept in sync with the theme source - NOT an exhaustive enumeration of every hook.
`wppilot/avada-list-portfolio-items`List Avada Portfolio Items	Compact enumeration of `avada_portfolio` CPT posts. Returns rows with id, title, slug, status, modified, and the first assigned `portfolio_category` term. Paginated: default `limit=25`, hard cap 100. Use `status` to filter (default: any). This is inventory only - use `wppilot/get-content` to fetch the full block/shortcode content of a specific item.
`wppilot/avada-list-sliders`List Avada Fusion Sliders	Enumerates every Fusion Slider registered on this site. In Avada, a "slider" is a term of the `slide-page` taxonomy - this ability returns the slug + display name + numeric term id + slide count for each. Use before `avada-get-slider` (to know the slug) and before writing to `avada-edit-slider-settings`. Read-only; requires Fusion Core plugin active at min version.
`wppilot/avada-list-slides`List Avada Fusion Slides	Paginated enumeration of Fusion Slider slides (posts of type `slide`). Returns compact rows: id, title, slug, status, modified, and (for classification convenience) the parent slider slug/name if the slide belongs to exactly one slider. Filter by `slider` (slug or term id) to scope the listing to one slider; omit to list every slide on the site. `limit` is clamped to a hard maximum of 100 to keep responses agent-friendly (progressive disclosure - page through with `offset`). Read-only; requires Fusion Core plugin active at min version.

Avada writes

Ability	What it does
`wppilot/avada-edit-global-color`Edit Avada Global Color	Update a single AWB Global Color preset by slug (`color1`..`colorN`). At least one of `label` / `color` must accompany `slug`. `color` accepts any CSS color string the theme will echo verbatim (typical: `rgba(r,g,b,a)` or `#rrggbb`). Read-modify-write on `fusion_options.color_palette`: only the target slug is mutated, siblings preserved. `changed: false` on an idempotent no-op (same value stored). Post-write flushes `fusion_dynamic_css` + fires `fusion_cache_clear` so the front end serves fresh CSS.
`wppilot/avada-edit-global-typography`Edit Avada Global Typography	Update a single AWB Global Typography preset by slug (`typography1`..`typographyN`). At least one field must accompany `slug`. Read-modify-write on `fusion_options.typography_sets` - only the target preset is mutated. `changed: false` on an idempotent no-op. Post-write flushes Fusion cache. Values shape maps to Avada storage keys: `family`→`font-family`, `size`→`font-size`, `weight`→`font-weight`, `lineHeight`→`line-height`, `letterSpacing`→`letter-spacing`, `textTransform`→`text-transform`.
`wppilot/avada-edit-slide`Edit Avada Fusion Slide	Partial-merge update on a Fusion Slider slide (`slide` post). Only the keys passed in `values` are written; siblings are preserved. Keys are validated against the writable-slide-keys whitelist (`avada_writable_slide_keys()`) - unknown keys reject the ENTIRE batch (all-or-nothing, no partial writes). Each value is sanitized against its declared type (string/url/color/bool/int/enum) before persistence - a value that cannot be normalised safely also rejects the entire batch. Post-write flushes the `avada` wp_cache group + fires `fusion_cache_clear`. Idempotent: same values → `changed: false`. Requires Fusion Core plugin active at min version.
`wppilot/avada-edit-slider-settings`Edit Avada Fusion Slider Settings	Partial-merge update on a Fusion Slider `_fusion` term_meta bag - the dimensions, animation, autoplay, and navigation settings the slider ships with. Only the keys passed in `values` are written; siblings are preserved. Keys are validated against `avada_writable_slider_setting_keys()` - unknown keys reject the ENTIRE batch. Each value is sanitized against its declared type before persistence. The read-modify-write cycle is serialized against concurrent editors of the same slider (TOCTOU lock - two callers editing different subkeys of the same term will not clobber each other). Post-write flushes the `avada` wp_cache group + fires `fusion_cache_clear`. Requires Fusion Core plugin active at min version.

Destructive Avada calls

Ability What it does

wppilot/avada-set-theme-optionsSet Avada Theme Options Whitelist-only write to fusion_options. Accepts a settings map of key → value; every key must be on the curated allowlist (~20 safe scalars - colors, layout, header/footer toggles, extras) AND must NOT be on the reserved list (raw custom_css / custom_js / license fields). Response reports written[] (keys whose stored value actually changed) and unchanged[] (submitted keys already at target - idempotent no-op). Cache flush after every write. The whole batch runs inside a fusion_options row lock so it never interleaves with a concurrent edit-global-color / edit-global-typography / set-theme-options call on the same row.

Ability	What it does
`wppilot/avada-set-theme-options`Set Avada Theme Options	Whitelist-only write to `fusion_options`. Accepts a `settings` map of key → value; every key must be on the curated allowlist (~20 safe scalars - colors, layout, header/footer toggles, extras) AND must NOT be on the reserved list (raw `custom_css` / `custom_js` / license fields). Response reports `written[]` (keys whose stored value actually changed) and `unchanged[]` (submitted keys already at target - idempotent no-op). Cache flush after every write. The whole batch runs inside a `fusion_options` row lock so it never interleaves with a concurrent edit-global-color / edit-global-typography / set-theme-options call on the same row.

For the task-level view of Avada, with worked requests and what to check afterwards, see Avada integration page.