Elementor

Elementor pages an agent can edit widget by widget.

Documents, elements, widget settings, global tokens and display conditions. Elementor stores a page as one serialised tree, so every write here snapshots the whole document — which is why a rollback restores the page rather than a fragment of it.

Agencies maintaining Elementor builds, where the alternative is an agent that cannot see inside the page at all.

4 jobs

What people actually ask for.

Each of these is carried by named operations that exist in the release you can download today. The ids under every answer are the calls involved — nothing here is a plan.

“Change the headline in the hero section.”

The composition is read, the element found by search rather than by guessing an id, and its settings updated against the schema Elementor itself publishes for that widget.

  • elementor-composition-get needs edit_post
  • elementor-element-search needs edit_post
  • elementor-widget-settings-update needs edit_post

“Duplicate the testimonial block and move it above the pricing table.”

A duplicate and a move, both against the live tree, both reversible.

  • elementor-element-duplicate needs edit_post
  • elementor-element-move needs edit_post

“Change the brand blue everywhere.”

Global colour and typography tokens are written at source. This is declared high risk — a small edit with a site-wide blast radius — and is snapshotted accordingly.

  • elementor-global-tokens-get needs edit_theme_options
  • elementor-global-colors-update needs edit_theme_options
  • elementor-global-typography-update needs edit_theme_options

“What settings does this widget even accept?”

The control schema is fetched from Elementor rather than assumed, which is the same reason this whole surface publishes schemas at all.

  • elementor-control-schema needs edit_posts
  • elementor-widget-availability needs edit_posts
The shape of it

19 operations, 9 of them reads.

Documents and elements, widget settings, global colour and typography tokens, and theme-builder display conditions.

Needs: Elementor 3.0 or newer. Where it is absent the operation refuses by name, rather than failing obscurely.

Every operation, with its policy

Reads

9 operations that only report. A read still asks WordPress for a capability against the object.

Writes

10 that change something — each one previewed as a diff, snapshotted, verified by reading the site back, and reversible from wp-admin.

Tier

Free, permanently. Nothing in this area moves into a paid tier later.

The limit

What it will not do here.

Elementor 3.0 or newer must be active. Where it is missing, every operation here refuses by name rather than failing obscurely.

Note 1

Elementor keeps a page as one serialised tree. Every write here re-serialises that tree from a snapshot of the whole document, which is why a rollback restores the page rather than one widget.

Note 2

elementor-control-schema exists so an agent asks Elementor what a widget accepts instead of guessing a control name — the same reason this surface publishes schemas at all.

Note 3

A global colour or typography change is declared high risk: a small edit with a site-wide blast radius.

Next

Try it, or read further.

Get the free plugin How a write is guarded