Avada Studio is Avada’s own catalog of ready-made templates, sections and elements, and finding a pricing block that fits usually means scrolling the Studio panel inside the builder, importing a few to compare, and cleaning up the ones you did not use. An agent can search the catalog by type and title, show you the candidates with their previews, and import only the one you choose.
The Studio import is the one Avada tool that no Enable all button ticks, and the Studio list stays refused until it is on, so the site owner switches it on by itself. Avada, not this plugin, makes the requests to its servers.
I want a [pricing] section from Avada Studio on our [Plans] page (id [64]),placed [after the intro text].
List Avada Studio items with avada-list-studio-items, type [fusion_element],searching for [pricing]. Show me each match's title, and its category andpreview link where Avada has them, and wait for me to pick one. Do not import anything yet.
When I pick one, import it with avada-import-studio-item [with imageplaceholders]. Tell me the new Library item's id and whether it was importedbefore.
Then read the Plans page with avada-get-page-content and include_structure,find [the intro text], and tell me the index and placement you will use. Waitfor my go, then place the item with avada-insert-library-item and the pagefingerprint from that read. Give me the restore_revision_id.Why this is safe to run
Each step waits for you. The list is a read, and you pick the item from its preview before anything is imported. The import is idempotent: an item imported before is not imported again, and the response says so. Only the item’s own post is confirmed, by its type and Avada’s Studio marker.
The import and the placement are separate writes, so a section you decide against never reaches a page. The placement runs the same checks as any Library insert: Avada’s nesting rules, the page fingerprint, and the content checks for users without unfiltered HTML.
The Studio import is an ordinary write, not on the high-risk list, but it is the only tool that no bulk enable control ticks, and its switch is also what lets the Studio list answer at all. Both Studio tools need the manage-options capability, and every call is in the Activity Log.
If the section is already in your Library, skip the import and use add a saved section to an Avada or WPBakery page.
Already connected? From an admin connection, ask your agent for the “import an Avada Studio section” recipe, name the kind of section and the page, and it runs the same pick-first flow on your own site.