You already built the testimonial strip once and saved it to the library. Now it needs to go on six landing pages, under the pricing table, and dragging it in by hand on each one is slow. Both builders keep saved sections you can reuse: Avada in its Library, WPBakery in its template library (or Templatera, when that add-on is active).
This prompt finds the saved item, agrees on the exact spot, and places it there.
I want to add our saved [Testimonials] section to the [Pricing] page(id [77]), directly [after] the [pricing table].
First tell me which builder owns the page. If it is Avada, list the AvadaLibrary with avada-list-library; if it is WPBakery, list the templates withwpbakery-list-templates. Show me the items whose names match and wait for meto pick one. Tell me if the Avada item is global, because then the page willshow the shared item rather than a copy.
Read the page outline with include_structure and find the [pricing table].Tell me its index and tag, and the placement you will use. Do not insertanything until I say go. Then insert the item with the page fingerprint fromthat read. Afterwards, read the outline again to confirm where the sectionlanded, and give me the restore_revision_id.Why this is safe to run
The library list and the page read change nothing, and you pick the item and the anchor element before any write. The insert needs the page fingerprint from the last read, so a page someone edited in the meantime is refused with nothing saved. Other elements’ positions can shift after an insert, which is why the prompt reads the outline again before anything else happens.
The content checks come from the builder tools themselves. An item may hold at most 50 elements nested at most 6 deep. For a user who may not post unfiltered HTML, an item’s text may hold no square bracket, percent-encoded bracket, data-* attribute, unfinished tag or HTML WordPress would remove. An Avada global item it shows by reference gets the same access and content checks, at any depth, and a reference loop is refused. After a WPBakery insert, the page’s generated CSS is rebuilt.
When revisions are on, the write returns restore_revision_id, and Restore revision takes the page back to how it was. These inserts are not in the Changes tab. Each tool is off until you switch it on, runs as the user you bound the agent to, and is logged.
To bring in a ready-made section from Avada Studio first, see import an Avada Studio section and place it.
Already connected? Ask your agent for the “add a saved section” recipe, name the section and the page, and it runs the same flow on your own site.