GoBuildWP

Page buildersPro

GoBuildWP Breakdance integration: requirements and coverage

A reference to Breakdance MCP abilities in GoBuildWP, organised around what Breakdance saves: a canvas per post, five template post types, a handful of prefixed option rows for classes, variables and global styles, and form submissions. Every write in this module asks for confirmation, so knowing which record a call reaches is the quickest way to decide whether to approve it.

AI clientyour-site.comVerify site policy

Make a small popup with a discount heading and show it only on single product pages.

  1. wppilot/breakdance-list-templatesRead

    Checks the existing popups first, so a second one is not created with the same purpose.

  2. wppilot/breakdance-create-templateConfirm first

    Creates a breakdance_popup post with a title. It starts with an empty canvas and no conditions.

  3. wppilot/breakdance-list-element-typesRead

    Returns the element types registered on this install, so the heading is added with a slug that exists here rather than a guessed one.

  4. wppilot/breakdance-add-elementConfirm first

    Adds a heading to the popup's canvas using the element slug returned by list-element-types. You confirm the call before it is written.

  5. wppilot/breakdance-list-template-conditionsRead

    Returns the condition catalogue for popups, so the single-product rule uses a condition this install offers.

  6. wppilot/breakdance-set-template-conditionsConfirm first

    Writes rule groups limiting the popup to single products, again after confirmation.

  7. wppilot/breakdance-get-templateRead

    Reads the saved settings back so the conditions can be checked as stored.

Proposed sequence from source declarations; not a recorded task or proof of client compatibility. Inspect saved state and browser or provider results separately.
Edition
Pro
Abilities
33
Requires
WordPress 6.9+, PHP 8.0+, Breakdance 2.7.0+

Requirements and coverage

What this integration needs, and where the detail lives

Edition
Pro
WordPress and PHP
6.9+ and 8.0+
Version floor
Breakdance 2.7.0+
Abilities
33, listed in the reference

Limits

Read these before approving a Breakdance write

  • Every write ability in the module is marked destructive, from adding one element to editing global styles, so each call waits for an explicit confirmation. Reads never do.
  • The module needs Breakdance 2.7 or later, and does not load when the Soflyy engine is running in Oxygen mode.
  • A tree nested beyond PHP's JSON depth limit is refused before writing, rather than saved as an empty canvas.
  • Submissions can hold personal data, and deleting one does not remove its uploaded files. Keep that work to reading unless there is a specific reason.

Data model

A double-encoded canvas and five kinds of template

Breakdance saves a post's canvas in the _breakdance_data meta field. The stored value is an envelope holding tree_json_string, which is itself a JSON string, so the tree is encoded twice. Decoded, it has a root node, a _nextNodeId counter and nodes shaped as an integer id, a data object with type and properties, and a children list. GoBuildWP decodes the whole tree, edits it, re-encodes it in the same shape Breakdance writes, then asks Breakdance to regenerate that post's CSS; if regeneration fails the write is kept and the failure comes back as a warning.

Templates, headers, footers, popups and global blocks are five post types, breakdance_template, breakdance_header, breakdance_footer, breakdance_popup and breakdance_block, each with a canvas and a _breakdance_template_settings field for conditions and priority. Global classes, variables and global styles are option rows written through Breakdance's own data layer, which prefixes them with breakdance_. Form entries are breakdance_form_res posts.

Worked example

A promotional popup for product pages

Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.

A popup that renders only where its conditions match. Each confirmed step has its own before-image; deleting the popup later trashes it unless you ask for a forced delete.

A CSS-regeneration warning means saved content may not render as intended. Check popup trigger and activation prerequisites, then inspect both included and excluded URLs; saved conditions alone do not establish displayed behavior.

  1. breakdance-list-templates

    Checks the existing popups first, so a second one is not created with the same purpose.

  2. breakdance-create-template

    Creates a breakdance_popup post with a title. It starts with an empty canvas and no conditions.

  3. breakdance-list-element-types

    Returns the element types registered on this install, so the heading is added with a slug that exists here rather than a guessed one.

  4. breakdance-add-element

    Adds a heading to the popup's canvas using the element slug returned by list-element-types. You confirm the call before it is written.

  5. breakdance-list-template-conditions

    Returns the condition catalogue for popups, so the single-product rule uses a condition this install offers.

  6. breakdance-set-template-conditions

    Writes rule groups limiting the popup to single products, again after confirmation.

  7. breakdance-get-template

    Reads the saved settings back so the conditions can be checked as stored.

Questions

Breakdance questions

Why is _breakdance_data encoded twice?

That is how Breakdance saves it: an outer object whose tree_json_string holds the tree as a JSON string. GoBuildWP keeps that shape on write, because re-encoding the inner string differently would leave a canvas Breakdance cannot open.

Can the agent edit a Breakdance global block?

Yes. A global block is a breakdance_block post with its own canvas, so the element calls work on it by post id, and every page embedding the block shows the change.

Does editing global settings merge my typography?

Only at category level. Passing typography replaces the whole typography category. Read it with get-global-settings, change the part you need, and send the full category back.

Breakdance documents its own MCP agent connection. GoBuildWP's module is a separate integration with the GoBuildWP credential, ability controls and cross-plugin workflow. Installing one does not configure the other. Breakdance agent connection guide

Other plugins

Breakdance's own agent route and Oxygen

  • Breakdance documents its own agent connection through an Agent Connector plugin and an application password. It is configured separately; installing GoBuildWP does not set it up, and neither does the reverse.
  • Oxygen 6 runs on the same engine. GoBuildWP loads its Breakdance module or its Oxygen module, never both, so option rows are always read with the prefix of the builder actually running.

Where these facts come from

GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.

Breakdance is a separate product; no partnership or endorsement is implied.

Try it on Breakdance in Read Only first