Asana Manager: Know Your Asana Connection Is Healthy
Is Asana the problem? Read-only checks and a clear verdict, on request.
The Asana Manager is the Asana integration health check in the Ai1 platform by MyZone AI: when you ask, it runs read-only checks on your Asana connection and the Asana tools your agents rely on, gives a pass, warning or fail for each check and sends any fix to its owner.
You learn quickly whether a problem is the Asana connection or something else, instead of guessing.
Nothing in Asana is touched
Every check is read-only, so your tasks and projects are never created, changed or completed by it.
The right fixer, first time
Problems go straight to whoever fixes them, with the evidence attached, instead of bouncing around.
Meet your agent
Get to know Freya
Freya checks that your Asana connection works and that the tools your agents use with Asana are healthy. She runs read-only checks, gives a clear pass or fail and never touches your tasks.
AI agent. Fictional persona; not a real person.
Freya, the persona of the Asana Manager
Name
Freya M.
Role
Asana Specialist
Experience
9 years
Work history
Project operations coordinator at an architecture practice Tools administrator at a marketing agency
Personality
Read-only and careful, straight answers
Based in
Glasgow, United Kingdom
Why Freya has a personality
AI does better work as a specific expert, so the Asana Manager works as Freya (Asana Specialist, Glasgow, United Kingdom). You can rename Freya or change the personality, experience and profile settings at any time.
Whether Asana is healthy, or why something using Asana stopped working
What it checks
The connection, the login, your workspace and main project, and the shared Asana tools
The verdict
Pass, warning or fail for each check, with the time it ran; 'could not check' is kept apart from 'broken'
When it breaks
The affected agents are named and the evidence goes to the Developer or the Skill Manager
Expired login
Explained in plain English; you reconnect in your browser through a secure form
What it never does
Create, change or complete anything in Asana, or see your Asana login
Capabilities
What the Asana Manager does for you
Checks the connection end to end
Confirms the connection exists, the login still works, your workspace and main project can be found, and the shared Asana tools load.
Gives a clear verdict
Each check comes back pass, warning or fail with the time it ran. A check that could not run, such as during a network blip, is kept separate from one that is broken.
Keeps a list of the Asana tools
An up-to-date list of the Asana tools on your Ai1 server, what each one needs and which agents use them, so a failure can be traced quickly.
Sends fixes to the right owner
Names the affected agents and passes the evidence to whoever fixes it: the Developer for code, the Skill Manager for tool changes.
Keeps your login out of its hands
If the Asana login has expired it tells you in plain English. You reconnect in your browser through a secure form, and it never sees or asks for the login.
How the Asana Manager differs from checking Asana by hand
Checking by hand usually means opening Asana, guessing and asking around. The Asana Manager runs the same read-only checks every time: connection, login, workspace, main project and the shared Asana tools. You get pass, warning or fail for each, with the time it ran and the agents affected. Broken tools go to their owner with the evidence, and nothing in Asana is created, changed or completed by it.
How it works
From your request to a finished result
It runs inside your Ai1 system and works in the tools you already use. You ask, it works, it reports, and it stops for your OK where it matters.
Tap the diagram to enlarge it
Step 1: You ask
You ask whether Asana is healthy, or report that something using Asana has stopped working.
Step 2: Read-only checks
It checks the connection, the login, your workspace and main project, and the shared Asana tools.
Step 3: Verdict
Pass, warning or fail for each check, with the time it ran.
You approve
Step 4: Route the fix
Broken tools go to their owner with the evidence. An expired login comes to you as a step to complete in your browser.
When to use it
Hand these situations to the Asana Manager
Illustrative photo. Ask whether the link to your project board is still working.
If this is you…
…here's what it does
An agent that uses Asana has stopped updating
It checks whether the Asana connection is the cause and lists which agents are affected.
Your weekly scorecard did not update
It can find, for example, that the Asana login has expired, name the affected agents and explain how to reconnect in your browser.
You changed your Asana workspace or projects
It confirms your agents can still find what they need.
You want to know which agents rely on Asana
It gives you the current list of Asana tools and the agents that use them, as counts only, with no task contents.
What you get
A pass, warning or fail verdict for each check, with the time it ran
The exact check that failed and the agents affected
An inventory of the Asana tools on your Ai1 server and the agents that use them
A plain English browser step when the Asana login needs reconnecting
The evidence, handed to the owner of each fix
What it won't do
✕Create, update or complete tasks in AsanaHandled by: Your team, in Asana
✕Set up Asana for a new account during onboardingHandled by: The Onboarding Agent
✕Change the code behind the Asana toolsHandled by: The Developer
Example Asana health check
Example: Asana connection health check
Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended.
What it was asked: The weekly scorecard didn't update this morning: is Asana the cause, and if so, what needs fixing and by whom?
Example report
The answer in one screenFirst check: login expiredA person reconnects, then it checks againTool inventory and who owns each fix
What it found: 3 findings, with the numbers
The Asana login had expired, so the scorecard agent and the project-update agent could not read Asana. That is why the scorecard was blank. Nothing in Asana was touched.
Your operations lead reconnected Asana through the secure browser form at 09:14. Asana Manager never saw the login. The re-check at 09:20 confirmed the login, the workspace and the main project.
One of the six shared Asana tools, the milestone reader, will not load because one of its files is missing. The evidence went to Developer; until it is fixed, project updates will lack milestone dates.
Asana Manager ran on request, using read-only calls only, and checked four things twice: that the connection exists, that the login works, that the workspace and main project can be found, and that the shared Asana tools load. It kept 'could not check' separate from 'fail', left the reconnect to a person through the secure form, and sent the broken tool to Developer rather than fixing it. It did not read task contents or rerun the scorecard, and because this example uses an invented company, no real Asana account was checked. Run date: .
Asana is a trademark of its owner. MyZone is not affiliated with or endorsed by Asana.
Want an Asana health check like this for your own Asana connection? Book an Asana Manager walkthrough.
Builds its weekly scorecard from your planning data, so a broken Asana connection is worth ruling out first.
Common questions
Frequently asked questions about the Asana Manager
How can I tell if our Asana connection is broken?
Ask the Asana Manager. It checks that the connection exists, the login still works, your workspace and main project can be found and the shared Asana tools load. Each check comes back pass, warning or fail with the time it ran, and a check that could not run is kept apart from one that is broken.
It reads only what a health check needs. Its reports list counts and identifiers, never task contents or client names.
Does Asana integration monitoring need to run on a schedule?
Not with the Asana Manager. It works only when you ask, in Control Room chat or its Slack channel, and runs no schedules of its own. Ask whenever something that uses Asana looks wrong, or after you change your Asana workspace or projects, to confirm your agents can still find what they need.
It never messages you on its own: it runs no schedules and posts nothing unless asked.
Who fixes an Asana tool when an AI agent cannot read Asana?
It depends on the cause. The Asana Manager names the agents affected and passes the evidence to the owner: the Developer for code, the Skill Manager for tool changes.
It does not fix broken Asana tools itself. It finds the problem and hands the evidence over, so the right owner can make the change.
What happens if our Asana login has expired, and can the Asana Manager edit tasks?
It tells you plainly and explains the browser step to reconnect. You reconnect through a secure form, and it never sees, stores or asks for the login.
It cannot create or update tasks in Asana. It is read-only, and creating and updating tasks stays with your team in Asana.
About Ai1
Do I get just the Asana Manager, or the whole platform?
The whole platform. The Asana Manager is not sold on its own: every Ai1 agent, including this one, is included on Developer Pro and every Fully Managed option, with no per-agent charge. Developer Core includes the development agents. Compare plans →
Two paths, one platform. Build it yourself on a developer plan, or let our team run your AI operations for you. Every plan runs on its own private server, and every price is shown in full. See Ai1 pricing →
Operations
Operations
Operations
Operations
Operations