Importing and exporting an agent

An Aidoo agent is fully described by a JSON file. You can export it from its page, read it, edit it in a text editor, version it with your code or hand it to a colleague, then import it into another workspace. The file follows the aidoo-agent/v1 format.

Three common uses:

• Duplicating across workspaces: an agent tuned on a first Odoo is reinstalled in a minute for another customer or another company.
• Keeping a history: one file per agent in a Git repository, and every change of mission or rule becomes a readable revision.
• Writing an agent outside the interface: an integrator, a script or an AI assistant can produce the file; Aidoo validates it on import and shows it in the creation wizard before anything is saved.

Exporting

Open the agent's page and click the JSON button (download icon) in the header. The browser downloads agent-<agent-name>.json. Export is reserved to workspace owners and administrators.

Importing

In Agents > New agent, choose Import a JSON file (aidoo-agent/v1). Aidoo checks the file, then opens the creation wizard prefilled. Nothing is saved at that point: you designate the Odoo identity, choose the Odoo users who will see the agent in the widget, review every step, then Create the agent creates and activates it, like any other agent. An invalid file is rejected with the offending field.

If the file does not specify permissions.learning (and the agent is not in workflowsOnly mode), it starts in learning mode and the file's rules serve as starting rules.

The file

{
  "schema": "aidoo-agent/v1",
  "exportedAt": "2026-09-16T10:00:00.000Z",
  "source": { "agentId": "64a1b2c3d4e5f6789012345a", "workspace": "ACME" },
  "agent": { "...": "the configuration, detailed below" }
}

A hand-written file only needs schema and agent.

What the export never contains

The file is a portable configuration, not a vault. It contains:

• no Odoo identity: on import, you choose again the member whose rights the agent uses;
• no API key, token or connection credential;
• no skills, no knowledge sources, no Drive files: they belong to the workspace; reattach them after import;
• no agent group: groups are specific to a workspace; put the agent in a group after import;
• no connection to external apps: the file keeps each app's name and the selected tools, not the connected account; connect the app under Integrations in the destination workspace;
• no execution state: mission history, learning-mode observations, error counters, event cursors.

Two fields deserve a look before sharing a file: notifications.email.recipients (e-mail addresses) and assignedOdooLogins (Odoo logins of the users who see the agent in the widget). Clear them if the file changes company. collaborators are agent ids from the original workspace: on import into another workspace, those that do not exist are simply ignored. allowedWorkflowIds also point to workflows of the original workspace: select them again at the Permissions step. drive.folders paths are kept as is: check that those folders exist in the destination Drive.

Full example

The "Overdue invoice follow-up" agent from the gallery, as it exports:

{
  "schema": "aidoo-agent/v1",
  "agent": {
    "name": "Overdue invoice follow-up",
    "avatar": { "seed": "finance-relance-impayes" },
    "mode": "scheduled",
    "instructions": "Every morning, list customer invoices (account.move, move_type='out_invoice') that are posted, unpaid and past their due date. For each one, add a chatter note summarising the delay (days, amount) and schedule a follow-up activity for the responsible salesperson. End with a summary: number of overdue invoices, total amount, top 5 customers concerned.",
    "style": { "preset": "descriptive" },
    "model": { "provider": "auto", "modelId": "auto" },
    "environment": "production",
    "timezone": "Europe/Paris",
    "trigger": { "cron": "0 8 * * 1-5" },
    "permissions": {
      "workflowsOnly": false,
      "webAccess": false,
      "requireApproval": false,
      "email": false,
      "emailMode": "propose",
      "document": false,
      "askUser": false,
      "rules": [
        { "scope": { "groupKey": "facturation" }, "operations": ["query", "read"] },
        { "scope": { "models": ["mail.activity"] }, "operations": ["query", "read", "create"] },
        {
          "scope": { "models": ["account.move"] },
          "operations": ["query", "read", "write"],
          "valueConditions": [{ "field": "move_type", "operator": "=", "value": "out_invoice" }]
        }
      ],
      "learning": { "active": true }
    },
    "limits": { "timeoutSecondsPerRun": 300, "maxAutoEmailsPerRun": 10 },
    "autoPause": { "enabled": true, "maxConsecutiveErrors": 3 },
    "activeHours": { "enabled": false, "days": [1, 2, 3, 4, 5], "start": "08:00", "end": "18:00" },
    "notifications": {
      "email": { "enabled": false, "recipients": [], "frequency": "onlyOnError" },
      "odooChatter": { "enabled": false },
      "odooDiscuss": { "enabled": false },
      "questions": { "widget": true, "email": false }
    },
    "assignedOdooLogins": [],
    "commands": [
      {
        "id": "follow-up-customer",
        "label": "Follow up a customer",
        "prompt": "Follow up every overdue invoice of this customer and summarise what you did.",
        "variables": [{ "name": "Customer", "required": true }]
      }
    ]
  }
}

Field reference

Values marked "default" can be omitted: Aidoo fills them in on import.

Identity and mission

Model and environment

Trigger (trigger)

Permissions (permissions)

Unless in workflowsOnly mode, an agent needs at least one rule, one external app, web access, Drive access or learning mode.

Each rule:

Limits and automatic pause

Active hours, notifications, visibility, commands

Compatibility

• Unknown fields are ignored on import: a file produced by a newer Aidoo version imports, minus the settings it added.
• Missing fields take their default value.
• A file whose schema is not aidoo-agent/v1 is rejected. A new version number will only be introduced for an incompatible change, with a bridge from v1 files.
• Export goes through the same validation as import: an exported file always imports back.

Next step

• Creating an agent: the other creation paths
• Rules and permissions: building safe rules