Unstructured: The MyDataWork Blog

Everyone is racing to give AI agents more autonomy. The hard part isn’t wiring an agent to tools — it’s deciding which agentic use case is worth building, which systems it needs, and what guardrails keep it safe. Agent Studio is the place you answer those questions, from the systems you already work with, before anyone writes a line of agent code. Addressing the gap before the runtime Industry guidance has converged on a clear

Your data work has never had a home before. That’s not a criticism of your tooling — it’s the simple reality this product exists to change. The spreadsheets, queries, dashboards, and notebooks that run your part of the business live in folders and memory, and until now there’s been no system whose job was to catalog that work, connect it to business value, and keep the context alive. Which means that when you open MyDataWork

Most data-lineage tools are strongest where the work is governed, centralized, and platform-visible: warehouse tables, SQL transformations, dbt models, semantic layers, and dashboards connected to known sources. Inside that world, they can be genuinely useful. But a lot of analytical work still happens outside that clean boundary. It happens in Excel, in Alteryx, in local Python notebooks, in exported files, in one-off models, and in workflows that move between desktop tools, cloud warehouses, and BI

Open any analyst’s working folder and you will find the same thing: spreadsheets, SQL scripts, Alteryx workflows, dashboards, notebooks, a model or two, and a handful of exports. Each file is the product of real effort and real judgment. And not one of them can tell you why it exists. A file named dc_starting_inventory.xlsx does not record that it supports a weekly inventory decision worth $30,000 a year. A network-optimization workflow does not note who

How MyDataWork Applies AI to Real Data Work Most software that advertises AI starts with a chat box and leaves the rest to you. MyDataWork has an AI help assistant too, because users should be able to get guidance wherever they are in the app. But the assistant is not the main AI story. It is the help layer. The deeper AI story is what happens when AI is built directly into the workflow itself. That

Introducing Agent Access in MyDataWork: a way to let an AI agent read the context of your data work — what you’re working on, how it connects, and what it’s for — without ever exposing your data. The hardest part of putting an AI agent to work on real analytical problems isn’t the model. It’s context. An agent can be capable and still useless if it doesn’t understand the work it’s stepping into — which