Wialon Hosting AI agent connector: let your agent operate Wialon

The Wialon Hosting connector gives your flespi AI agent access to a Wialon Hosting account: Wialon documentation and API expertise plus direct work with the account data on your behalf. Use it to manage a Wialon Hosting account paired with flespi — or on its own, without any flespi pairing.

New to flespi AI agents? Read the flespi AI agents article first: what agents are, how they reason and sleep, and how approvals keep you in control. This article covers the Wialon Hosting side of the story.

1. Connect the account

Two configuration fields:

• token — a Wialon Hosting access token. Mint one via the login form on your datacenter's domain (the link opens the Europe 1 one; for another datacenter replace the domain), then copy access_token from the redirect URL. Use access_type=-1 for full access; duration=0 makes the token unlimited (auto-deleted after 100 days of inactivity).
• datacenter — the Wialon Hosting installation your account lives on: Europe 1 (hosting.wialon.com, the default), Europe 2 (hosting.wialon.eu), Europe 3 (hosting.wialon.org), USA (hosting.wialon.us), or KSA (ksa-hosting.wialon.com). A mismatched datacenter fails the login.

Copy the token right from the address bar after the login:

Create a connector of the wialon_hosting type with the token and the datacenter:

Assign the connector to your agent (create one if you have none yet), choosing the rule for the account-changing Wialon API calls:

The token defines the ceiling: the agent works strictly within the token's access scope and recommends a broader token when a task is out of reach, rather than attempting calls that will fail. An expired or revoked token surfaces to the agent immediately — it will ask you to reconnect the connector with a fresh one.

2. Work with the agent

The agent knows Wialon: it consults the official Wialon documentation and API reference on its own, so you can discuss units, resources, users, geofences, sensors, notifications, and reports the way you would with a Wialon engineer:

Reading the account is free and autonomous: the agent searches items, loads messages, executes and reads reports, and analyzes the results computationally — all through a read-only surface that physically cannot change anything:

When the account is paired with flespi, the agent reasons across both systems: for example, it checks how flespi data lands in Wialon. The connected account's data stays between you and the agent: it never leaks into other accounts or shared knowledge. Nothing on the Wialon side wakes the agent — for a monitoring task it checks the account on its own schedule.

Every account-changing Wialon API call goes through the agent operations ACL as the wialon_hosting_api_mutate operation type, and by default each call becomes an approval request — you review the exact call and its parameters before approving:

Mind what the default protects before relaxing it: the mutation surface includes commands to physical devices, token operations, and account and billing changes. With the rule switched to "allow", the agent executes all of these without asking. Two approvals later, one for the unit creation and one for its unique ID setup, the requested change is live in Wialon:

Executed mutations land in the agent conversation history as wialon_hosting_api_mutate_executed records:

Every Wialon API call the agent performs, reads included, is recorded in the connector logs with the operation, target, and result:

The Wialon Hosting connector is one of several an agent can hold: browse the full connector list to give your agent more capabilities.

Subscribe to the flespi AI and MCP change log to stay in sync with any updates.