elementor/import-template imports an Elementor template from a JSON export, regenerating element IDs to avoid collisions.
It creates a new template rather than overwriting anything.
At a glance
| Ability | elementor/import-template |
| Toolset | Elementor — toolset/elementor |
| Group | Elementor › Templates & Theme Builder |
| Requires | Elementor, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Element IDs must be unique within a document. Two elements sharing an ID is a state Elementor does not expect, and the symptoms — an edit landing on the wrong element, a duplicate that disappears — are hard to trace back to the cause.
An export carries the source site’s IDs, and importing them unchanged would eventually collide — particularly if the same template is imported twice, or if the source and target are the same site.
So IDs are regenerated on the way in, which also means importing the same export twice produces two independent templates rather than a conflict.
What does not come across is anything the export could not carry: Pro widgets on a site without Pro, media referenced by attachment ID, and the kit’s global colours and typography. A template that looked right on the source can look quite different here, and the difference is usually the kit.
Checking elementor/get-style-guide on both sites explains most of those differences before they surprise anybody.
Not idempotent — each import creates a template.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
export | object | Yes | A payload from elementor/export-template. |
title | string | No | Override the imported title. |
What comes back
| Name | Type | What it is |
|---|---|---|
template_id | integer | The imported template. |
template_type | string | Its type. |
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:
Import this template export.
It resolves to one call:
{
"ability": "elementor/import-template",
"parameters": {
"export": {}
}
}Worth knowing
- IDs are regenerated, so importing twice is safe and produces two templates.
- Pro widgets, media IDs and kit styling do not come across.
- Compare style guides when an import looks wrong.
- Not idempotent.
Related abilities
- Export Elementor Template — produce the payload
- Get Elementor Style Guide — why it may look different
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category