elementor/get-template returns a single Elementor template with its metadata, its display conditions, and optionally its full document payload.
The payload is optional because it is large and usually not what you need.
At a glance
| Ability | elementor/get-template |
| Toolset | Elementor — toolset/elementor |
| Group | Elementor › Templates & Theme Builder |
| Requires | Elementor, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Most questions about a template are about its metadata: what type it is, whether it is published, and — for Theme Builder templates — where it applies. All of that is small.
The document is the whole design, which on a page template is a substantial JSON tree. Fetching it by default would make every listing-adjacent read expensive for no reason.
Theme Builder templates take effect through display conditions: rules saying which parts of the site a header, footer, single or archive template applies to. A template with no conditions is a template that renders nowhere.
So the conditions come back by default. “Which header is this and where does it show” is the question, and answering it should not require a second call.
Take the payload when you are exporting, duplicating by hand, or inspecting the structure — and use elementor/export-template when portability is the point.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
template_id | integer | Yes | The template post ID. |
include_data | boolean | No — defaults to false | Include the full _elementor_data payload. |
What comes back
| Name | Type | What it is |
|---|---|---|
template | object | The template with its metadata and conditions. |
data | array | The document payload, when requested. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
What is template 640 and where does it apply?
It resolves to one call:
{
"ability": "elementor/get-template",
"parameters": {
"template_id": 640
}
}Worth knowing
- Conditions come back by default; the document payload does not.
- The payload is large on page templates.
- For moving a template between sites, export rather than reading the payload.
- Read-only.
Related abilities
- Export Elementor Template — for portability
- Get Theme Builder Conditions — the conditions alone
- Update Elementor Template — change it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category