Your Agent. Your Data. One View.
Your goal
Build a Dashboard for Your AI Agent
Kydro Recommendation
A practical AI setup for achieving this goal.
Turn your Agent's results into a clear dashboard with key insights, recommendations and history — accessible on desktop and mobile.
- Human reviewed
- Free options shown honestly
- Never ranked by commission
Before you build your dashboard
Your AI Agent already works: it gathers signals, prepares recommendations and stores reports. But its results still live in tables and files. If you don't have an Agent yet, start with Build Your Own AI Market Radar.
A dashboard is the presentation layer: one readable page showing status, key information, recommendations and history — on your computer and phone. You'll build it with your own AI tool, on your own data, against an agreed contract.
Kydro teaches you — it does not host your panel and never sees your data. Everything you build belongs to you.
Why this works
The secret is not “a pretty chart” — it is the data contract: an agreed field list both sides understand, the Agent and the panel. Thanks to it, a dashboard built on demo data later accepts real data without rework.
Honest limits: the panel presents results — it does not control the Agent, edit prompts or trigger costly processes. The “Refresh” button refreshes the view, not the Agent's work.
What you need
AI Agent results (or demo data first)
The first fully described Agent is Build Your Own AI Market Radar — you get a ready adapter for its data. Steps 1–4 work even without a live Agent, on the bundled demo file.
An AI app-building tool
One you already use for code or app work. You'll paste a single, complete Master Prompt into it — you don't write code yourself.
Safety rule no. 1
No keys, tokens or passwords ever go into browser code, repository files or Kydro. Secrets live in a password manager and environment variables. If anything asks you for a key — stop the process.
A quiet hour to start
Steps 1–3 are decisions and understanding the data — nothing to install. Building and connecting come later, at your own pace.
What you will have at the end
The result is concrete and belongs to you:
- a working, responsive dashboard with your Agent's results — status, key information, recommendations, history and the last successful sync time,
- a flow confirmed by your own test: one controlled Agent run and the new record visible in the panel,
- a reusable kit: the data contract, the adapter, the security and connection checklists and the test plan — ready for future Agents too.
Step 1
Choose your Agent and the dashboard's purpose
A dashboard without a purpose is a wall of ornaments. The five decisions in this step steer everything that follows — from design to tests.
Why this step matters
You start with decisions, not tools. The Brief is one sheet of answers the Master Prompt creator uses later — the more concrete the answers, the better the panel.
What to prepare
- 15 quiet minutes and the Dashboard Brief template (resource below).
- Awareness of what your Agent actually produces (peek at its latest report).
Tips
Pick at most THREE “must see first” items. A panel that shows everything shows nothing.
1.1
Which Agent, and what for
What you do: choose the Agent whose results you want to see. The first fully described choice is Build Your Own AI Market Radar — its data, adapter and examples are ready in this guide. The compatible-Agents list on this page will grow with future Kydro publications.
Why: the dashboard's purpose follows from the Agent's job. For a market radar the natural purpose is: “know in 30 seconds what changed and what to do about it”. Write your purpose as one sentence — the most important line of the Brief.
A question for you
When you want to check your Agent's results today, how many clicks and minutes does it cost you?
1.2
Local or online — a deliberate choice
Path A (local): the panel runs on your computer, no hosting and no fees; access is mainly from that computer. Path B (online/PWA): reachable from desktop and phone, pinnable to the home screen; needs hosting, authentication and an online data source.
How to confirm a good choice: if your Brief's “who will use it” answer is “just me, at my desk” — start with A (you can move to B anytime). If it is “me, also from my phone” — plan for B, but you'll still build the demo-data version first.
Kydro insight
The variant is a decision about ACCESS, not looks — the same panel can live locally and online.
A question for you
In what real situation would you open the panel from your phone — and is that a need or a “nice to have”?
Kydro Resources
You can continue if…
- The dashboard's purpose fits in one sentence.
- Variant chosen: local or online/PWA.
Dashboard Brief
One sheet of decisions: Agent, purpose, three key items, audience, variant. The Master Prompt creator on this page can fill the prompt with your Brief answers.
- Agent & purpose
- Three key items
- Variant: local / online
Done when: your Dashboard Brief is filled in: the chosen Agent, a one-sentence purpose, the three key pieces of information, the audience and the variant (local / online).
Step 2
Understand your Agent's data
Understand the data contract and you'll never guess when something breaks. This step turns “mysterious files” into a simple map you'll navigate to the end.
Why this step matters
Four concepts are enough: DATA SOURCE (where the panel reads from), RECORD (one row, e.g. one signal), FIELD (one piece of information in a record) and CONTRACT (the agreed field list). JSON and CSV are just two notations of the same thing: JSON groups data in brackets, CSV in sheet-like columns; a database is a “guarded warehouse” of many records.
What to prepare
- The contract walkthrough (PL or EN) and the JSON Schema file downloaded (resources below).
Tips
Optional fields are not gaps — they are the engine's honesty. The Market Radar stores null instead of an invented date when a source shows none; a good panel then displays “no date”.
2.1
What the Market Radar really stores
What you do: open the contract walkthrough and compare it with the demo file's sections. You'll see data categories straight from the engine's implementation: runs (status, completion time, a labelled cost estimate), competitors (with approved/archived statuses), market signals (summary, novelty status, date confidence, impact level), recommendations (action, urgency, proposed/accepted/rejected/done status) and the report history.
How to confirm: find the demo signal with event_date: null and date_confidence: "unknown" — an optional field the panel must never require. The last sync time is sync.last_completed_at — the moment data last arrived correctly.
Common mistake
Designing the panel around fields the engine does not store. The contract lists everything that exists — if it's not there, the panel cannot show it.
A question for you
Which contract field brings you closest to your Brief's purpose — and is it required or optional?
2.2
The flow map — from Agent to view
Draw (literally, on paper) five boxes joined by arrows: AGENT (n8n does the work) → STORAGE (Data Tables) → ADAPTER (a small workflow that only reads and translates to the contract) → FILE/WEBHOOK (dashboard-data.json) → DASHBOARD (your view). Every future failure will be a break in one of these four arrows — and this map is where you'll look.
Security from day one: nowhere on this map do API keys or passwords appear in page code. The webhook credentials live in server-side configuration — the browser panel never knows them.
A question for you
Which arrow of your map feels most fragile today — and why?
Kydro Resources
Common mistakes
Skipping the contract — “it'll work out”.
Why it hurts: A single renamed field silently breaks the mapping: the panel shows blanks and nobody knows why.
How to avoid it: The JSON Schema is the referee — settle every field-name doubt there, not from memory.
You can continue if…
- The flow map is drawn.
- I know which fields may be empty.
Done when: you can draw the Agent → storage → adapter → dashboard → view map and point to three required and two optional fields in the contract.
Step 3
Design your dashboard
A paper design costs 20 minutes; redesigning a finished app costs an evening. Here you decide what the panel says in its first three seconds.
Why this step matters
A good panel reads top-down like a newspaper: 1) a status header with the sync time, 2) KPI cards (key numbers), 3) newest results, 4) recommendations, 5) history, 6) filters where lists grow long. Design the states separately: empty (“no records”), loading and connection error.
What to prepare
- Your step-1 Dashboard Brief and the demo data file (resource below).
Tips
For the Market Radar a proven first screen is: scan status and time, new-signal count, newest signals with impact level, “proposed” recommendations, watched competitors and the report history.
3.1
From Brief to sections
What you do: take the three “must see first” items from your Brief and give each a home: a number → a KPI card; a list of events → the newest-results section; an action to take → the recommendations section. Only then add the rest: history, filters, details.
What should appear: the sketch from this page's creator — a desktop layout (sections side by side) and mobile (one column), both with a visible “Demo data” label. If something doesn't fit on the phone — cut section content, don't shrink the font.
Kydro insight
Empty/error states are not decoration: without them the panel looks broken exactly when you most need to trust the data.
A question for you
What should your panel say in a week when NOTHING happened — so that silence is information too?
Kydro Resources
You can continue if…
- Section order settled (desktop and mobile).
- Empty/loading/error states planned.
Done when: your section layout is settled (from the summary down to the empty and error messages) and you know how it looks on desktop and phone — the creator on this page shows a demo-data preview.
Step 4
Build the dashboard
Here decisions become an application. The AI tool writes the code — your job is a good brief (you have one) and an honest acceptance test (you'll get the list).
Why this step matters
The Master Prompt is a complete specification: contract, sections, responsiveness, fallback states, the demo label, the no-secrets-in-code rule and the acceptance test. The creator on this page fills it with your Brief answers — copy and paste is all that's left.
What to prepare
- Your AI app-building tool open, with the JSON Schema and sample-data.demo.json at hand.
Tips
Report fixes one at a time and concretely (“on the phone the KPI card overflows the screen”) — AI tools then fix faster without breaking the rest.
4.1
Prompt, build and acceptance
What you do: copy the generated Master Prompt (the “Copy” button confirms with “Copied”), paste it into the AI tool and attach the schema plus the demo file. What should appear: a complete, runnable project with a start guide in its README.
How to confirm: run the acceptance test from the prompt's requirement 9 — desktop and phone, the demo label, the sync time, every section; then break the data path on purpose and check the error state. If it looks different: paste the exact error back into the tool and ask for a fix — one issue at a time.
Common mistake
Accepting a panel that “looks nice” but never passed the states test. A beautiful screen with a raw error instead of a message is a failure, not a success.
A question for you
What did the first bug the AI tool fixed at your request teach you?
Kydro Resources
You can continue if…
- The app passes the acceptance test on demo data.
- There are no secrets in the code.
Done when: the app runs on the demo file: it opens on desktop and phone, shows the “Demo data” label, the sync time and every section from your design.
Step 5
Connect the dashboard to real data
The most important technical stage: the moment the panel stops being a mock-up. One controlled write and one new record on screen — that is your proof.
Why this step matters
For the Market Radar the path is ready: the adapter (a small, read-only n8n workflow) translates the engine's tables into a contract-shaped file. Local variant: save the adapter's output as dashboard-data.json. Online variant: the adapter responds through a protected webhook and the panel fetches from its address.
What to prepare
- The adapter guide (PL or EN) open next to n8n; the connection and security checklists at hand.
Tips
Check the adapter's output on its own first (does the JSON contain your signals?), and only then connect the panel — you cut the problem in half.
5.1
The adapter and the source swap
What you do: following the adapter guide, point at the results storage, verify the field mapping (contract names are deliberately identical to the engine's tables) and swap the app's demo file for the real source. The webhook credentials go only into server-side configuration — never into page code and never into Kydro.
The “one real record” test: trigger one controlled Agent execution in n8n, refresh the panel after it completes and check two things: the new record on the list and the updated sync time. If it looks different: the troubleshooting guide walks the flow map — from the run's status to the data path. How to stop: the panel only reads, so closing the app breaks nothing in the engine.
Kydro insight
A new record + a fresh sync time visible TOGETHER is the only honest proof of a working connection — a pretty view alone proves nothing.
A question for you
A month from now, how will you know the panel shows the truth and not yesterday's copy of the data?
Kydro Resources
Common mistakes
Putting credentials into the app code “just for a moment”.
Why it hurts: Code travels: into copies, repositories, hosting. A secret in code sooner or later stops being a secret.
How to avoid it: An environment variable or hosting settings — from minute one, not “after testing”.
You can continue if…
- The connection checklist passed in full.
- The security checklist passed in full.
Done when: the demo label is gone and, after one controlled Agent run, the new record and a fresh sync time are visible in the panel.
Step 6
Test and launch the dashboard
A panel you don't trust dies within a week. The final test builds that trust: every state, both devices, both themes — once, properly.
Why this step matters
Four access levels, simplest first: a LOCAL dashboard (your computer only) → ONLINE (an internet address protected by a login) → PWA (the same page pinned to your phone's home screen) → a NATIVE app (App Store/Google Play — out of scope, because a private panel doesn't need one).
What to prepare
- The test plan (resource below) and the guide for your chosen path: local or online/PWA.
Tips
Maintenance is one weekly minute: glance at the sync time after the Agent's run. A fresh time = the whole chain is alive.
6.1
The final test and the upkeep plan
What you do: walk the test plan point by point — desktop and phone, light and dark mode, empty data, valid data, an incomplete record, a connection error, manual refresh and automatic sync if your setup supports it. Plus two trust checks: no horizontal scrolling and no secrets in client code.
How to confirm completion: every plan item gets its own “I saw it with my own eyes”. The upkeep plan: after each Agent run — a glance at the sync time; after each layout change — the short test; once a quarter — the full security checklist.
A question for you
Which test-plan item changed your trust in the panel the most — and what does that tell you about future projects?
Kydro Resources
You can continue if…
- The test plan passed in full.
- I know how to keep the panel alive.
AI Agent Dashboard — result card
An honest index of what you built: the brief, the understood contract, the design, the app, the real connection and the passed test — in one place. Kydro stores nothing for you; this summary stays with you.
- Agent & variant
- The real connection
- Tests & upkeep
Done when: the test plan passes in full, your chosen launch path (local or online/PWA) works, and you know what to check on future updates.
Dashboard creator
Fill in the Brief, preview the layout on demo data and copy a ready Master Prompt — filled with your answers.
1. Your Dashboard Brief
Saved on this device — like your progress.
2. Layout preview
New signals
2
Recommendations
1
Competitors
5
Newest signals
Konkurent A — 89 zł [DEMO]
Konkurent B — Mokotów [DEMO]
Recommendation
Kontroferta wartościowa [DEMO]
A sample sketch on fictional data only — not your Agent's results.
3. Your Master Prompt
Generated from your answers above. Copy it into your AI app-building tool; attach the JSON Schema and the demo data file (resources in steps 2–3).
Fill in the Agent and the purpose to generate the prompt.
Compatible Agents
This guide builds dashboards for Agents published in Kydro. The list grows with each published Agent — we only show the ones that really exist.
Build your personal AI library.
Save useful goals and come back whenever you need them.
Success Tips
Expert recommendations to help you reach your goal faster and avoid common mistakes.
Start
RecommendedDemo first, truth second
Build and polish on demo data — swapping in the real source is then one move, not a renovation.
Simplicity
RecommendedThree items first
A panel wins by selection: three things visible at once beat fifteen scrollable sections.
Trust
RecommendedSync time always on top
The last successful sync time is the whole chain's pulse — one glance tells you whether the data is alive.
Hygiene
Don't add sections “just in case”
Every section costs attention and upkeep. Add one only after its absence hurts you twice.
Security
RecommendedA quarterly secrets review
Once a quarter, walk the security checklist — especially after hosting or data-source changes.
Questions & answers
What people ask after finishing this goal
The questions that only come up once you have the whole picture.
To finish everything — yes, because step 5 connects real data. You can start earlier though: steps 1–4 work entirely on demo data, even before your Agent goes live.
If you have no Agent at all yet, build your first one with Build Your Own AI Market Radar.
Yes — that is the recommended order. The demo file is entirely fictional and contract-valid, so a dashboard built on it accepts real data later without rework. While demo data is loaded, the panel shows a permanent “Demo data” label.
No. The Agent gathers and analyses data; the dashboard only presents it. It is a separate, small application connected to the Agent's results through an agreed data contract. The Agent works the same with or without it.
n8n is the workshop: the automation runs and gets fixed there. The dashboard is the results window: readable cards, lists and statuses for a person who wants to SEE, not configure. You no longer need to open n8n just to review results.
Wherever your Agent writes it — for the Market Radar, in your n8n's Data Tables. The dashboard receives only an export (a JSON file or a protected webhook response) and writes nothing back. Kydro stores none of your data.
No. An AI tool writes the code from the ready Master Prompt — you make the decisions (what to show, where to run it) and perform the checklist tests. Every technical term is explained at first use.
Yes — that is the local path: the app runs on your computer at a local address (localhost), reading a JSON file or a lightweight SQLite database. No hosting fees, with the limitations described below.
For a local dashboard — yes: the panel lives only while your computer and the app are running. When the Agent, the data source and the dashboard all run online, the whole set works with your computer switched off.
Yes, in the online variant: the responsive app opens in your phone's browser and, as a PWA, can be pinned to the home screen. A local panel on your computer is not automatically visible on your phone.
A PWA is a website that behaves like an app: you install it from the browser, no App Store or Google Play, and updates arrive instantly. A native app goes through a store and a separate publishing process — unnecessary weight for a private dashboard.
The local path can run with zero fees. The online variant may cost: hosting, a database, a domain, authentication, heavier usage. Many services offer free starter plans — check their current limits and prices in official sources on the day you deploy, because they change.
As often as your Agent works — a dashboard cannot speed up its source. With the Market Radar, new results appear after every completed run (e.g. weekly). The panel can poll periodically or on a “Refresh” click; it always shows the last successful sync time.
Walk the flow map and find the last healthy stage: 1) did the Agent's run actually complete? 2) did the adapter produce a fresh export? 3) is the dashboard reading the right source? The troubleshooting guide walks through each point.
By three things at once: the permanent “Demo data” label, the demo: true field in the data file and the [DEMO] markers in the sample records. If the label persists after connecting the real source, the app is still reading the demo file.
Account passwords — in a password manager. Source credentials (e.g. the webhook login) — in environment variables or hosting settings, never in page code and never in files committed to a repository. You never paste secrets into Kydro — such a request means STOP.
Yes — the data contract is designed as a shared language. The first fully described Agent is the Market Radar AI (ready adapter); future Agents published in Kydro will be able to use this same guide with their own adapters.
In the base variant you build one panel for one Agent — simplest and clearest. Nothing stops you from repeating the process for a second Agent later, or asking the AI tool for a source-switcher view; treat that as a deliberate extension, not the starting point.
Yes. The layout is presentation only — the data and the contract stay untouched. Return to the AI tool with a specific request (“move recommendations above the signal list”) and re-run a short version of the test plan after each change.
In this guide — no. We build a PRESENTATION layer: the panel reads results and changes nothing in the Agent. The “Refresh” button refreshes the data view — it does not trigger the Agent's work. Controlling an agent is a separate, serious topic (permissions, costs, security) — we don't promise it until it is genuinely built.
A working, responsive dashboard showing your chosen Agent's real results: current status, key information, recommendations, history and the last successful sync time — on your computer and, in the online variant, on your phone. Plus the full kit: contract, adapter, checklists and the test plan.