WalkInto

Interact with the user's WalkInto.in account and helpdesk. There are two surfaces, and they share one Bearer token stored at ~/.config/walkinto/token:

1. MCP tools (preferred). The plugin wires up the WalkInto MCP server (~13 tools) over a bridge that reuses that same token. When logged in, the tools appear in your tool list namespaced under the walkinto server. Use them for every data operation below — they take structured arguments and return structured results, with no shell, paths, or flags.
2. Bundled Node.js scripts (fallback + token lifecycle). The same capabilities also exist as scripts in this skill's scripts/ directory. Use them whenever the MCP tools aren't in your tool list, and for the things MCP structurally cannot do — login and logout, which mint and revoke the token the MCP bridge depends on.

A token belongs to one WalkInto user; some helpdesk actions additionally require that user to be support staff (an admin) and return a clear "requires an admin token" error otherwise.

Terminology: throughout this skill, support staff means a human WalkInto helpdesk operator with admin rights — not an AI agent. (The underlying API names this role "agent"; you'll see that word in raw error text.) "You" here is the AI assistant acting on the logged-in user's behalf.

Choosing a surface

• Prefer the MCP tools for tours, knowledge base, and tickets when they appear in your tool list. Inspect each tool's input schema for exact parameter names rather than guessing.
• Otherwise just use the scripts — they cover every data operation and need no setup. (The bridge reads the token at session start, so the walkinto tools may not be present until a reload. This needs no action and no explanation to the user — the scripts work identically. Don't surface bridge/MCP mechanics unless the user explicitly asks about them.)
• Login uses the begin/complete flow below (only begin's link-click involves the user). Logout you just run.

Authentication