Import and export tag groups

Overview

Axon lets you export your tag groups to a JSON file and import tag groups from a JSON file. Use import and export to move tag configuration between environments (for example from a sandbox to production), share a curated set of tag groups across organizations, or keep a backup of your rules. Both actions are available from the toolbar on the Tags page in Axon.

Creating, editing, importing, and exporting tag groups requires Editor access to Axon. See permission levels by product for a full breakdown.

Export tag groups

Export downloads every tag group in your organization as a single JSON file.

Open the Tags page

Go to Axon → Tags.

Trigger the export

Use the export action in the toolbar. Axon downloads a file named axon-tags-export-<YYYY-MM-DD>.json.

The exported file is human-readable JSON. Each tag group entry contains its name, scope, intent filters, tag selection mode (winner_mode), active state, and every tag definition inside it — including rules, priorities, and dynamic-name configuration.

Import tag groups

Import replays a JSON file into your Axon configuration. Each tag group in the file is compared against your existing tag groups (by name) and gets one of three statuses: New, Overwrite, or Invalid.

Open the import dialog

On the Tags page, open the import dialog from the toolbar.

Upload a JSON file

Drop a .json file into the dropzone, or click to browse. Only JSON files are accepted, and only one file per import. Expand What should the data look like? below the dropzone to see a template of the expected structure.

Review the summary

Click Next. Axon validates the file and either imports it directly or shows a summary grouped by status:

New — the tag group name does not exist yet and will be created.
Overwrite — a tag group with the same name already exists and will be replaced, including all of its tag definitions and rules.
Invalid — the entry could not be imported (for example, missing required fields or invalid values). The reason is shown next to the row.

If every tag group in the file is New, Axon skips the review and imports immediately. If every row is Invalid, the dialog offers a Go back button so you can fix the file and try again.

Confirm the import

Click Import to apply the changes. New tag groups appear on the Tags page, and overwritten tag groups pick up the values from the file.

Overwrite replaces the existing tag group’s configuration and every tag definition inside it with the values from the file. Double-check the review step before confirming, especially when importing into production.

File format

The file must be a JSON object with a version, an exported_at timestamp, and a tag_groups array. Each entry in tag_groups describes a tag group and the tag definitions inside it.

{
  "version": 1,
  "exported_at": "2026-01-01T00:00:00Z",
  "tag_groups": [
    {
      "name": "Pricing inquiries",
      "intent_ids": ["request_simple_order"],
      "scope": "inbox",
      "scope_values": ["sales@example.com"],
      "winner_mode": "majority",
      "is_deployed": true,
      "tag_definitions": [
        {
          "name": "Urgent EU",
          "description": "Rush orders outside EU",
          "priority": 1,
          "is_fallback": false,
          "conditions": {
            "combinator": "and",
            "rules": []
          }
        }
      ]
    }
  ]
}

Field reference for a tag group:

name — the tag group name, used to match against existing groups on import. Required.
intent_ids — the intents the group is scoped to. Leave empty to apply to all intents in scope.
scope — either inbox or area, matching the tag group scope you set in the UI.
scope_values — the inbox addresses or area ids the group applies to.
winner_mode — how Axon picks a winner when several tags match. Corresponds to the tag selection mode.
is_deployed — whether the group is active. Inactive groups import in the same disabled state.
tag_definitions — the tags inside the group, including their rules, priority, fallback flag, and dynamic-name configuration.

Export your current configuration first, then edit the JSON. That gives you a valid template with your own tag group names, scopes, and rule structure to work from.

What’s next

Create and manage tag groups in the Axon UI.
Migrate existing tags from the legacy tag configuration.
Import and export intents using the equivalent flow for the intent tree.

​Overview

​Export tag groups

​Import tag groups

​File format

​What’s next

Overview

Export tag groups

Import tag groups

File format

What’s next