Remembers what happened around every flow run
Failed runs, stuck approvals and the messages around them, linked to the supplier or request each one touched. Ask weeks later and get the answer.
Ditto remembers what happens around your flows and their approvals, in Outlook, Teams, SharePoint and your other apps. Ask why an approval stalled and get the answer, with its sources.
Free plan, no card needed. See pricing for prepaid usage plans.
The flow still sends approvals to the previous Leeds cost-centre owner, replaced on 2 September, so nobody has responded. Anna flagged that the invoice is over the PO, and Norland Freight chased payment on 18 September.
List approvals pending for more than five days, with the reason each one is stuck, and email the digest to Hugo and Anna.
A flow run shows an approval was rejected. The reason sits in Teams.
Run history holds the error. Outlook, Teams and SharePoint hold the rest.
Each stuck approval starts with the flow's purpose, retold. So does every AI chat.
Approvals wait in someone's inbox until a supplier chases.
Failed runs, stuck approvals and the messages around them, linked to the supplier or request each one touched. Ask weeks later and get the answer.
Outlook, Teams, SharePoint, Excel and many more feed one memory, next to your flows. Ask about a supplier once and Ditto checks them all.
Send the Norland Freight approval to the new Leeds owner, fix the flow's approver and draft the reply to Norland.
Resends the approval, drafts the supplier reply and fixes the flow, then waits for your OK. Set routine Power Automate checks to run on a schedule.
Use a low-cost model for the Friday approvals check and failed-flow lists, or connect Claude and Cursor over MCP. Ditto brings the same context every time.
Ditto is for teams whose work spans several apps and several people. If the answer about a flow lives in its run history and somewhere else, Ditto keeps it in one shared memory: a second brain the whole team can ask.
Three steps, then it keeps working in the background.
Connect Power Automate from the Ditto app with your Microsoft work account. It starts read-only, and nothing is added to your flows.
Flows, runs, approvals, people and decisions from every app, linked and kept current.
Use the Ditto app, ask in Slack, or connect Claude and Cursor. It answers with sources and acts in Power Automate.
Copilot builds flows from a description, AI Builder adds models and prompts to flows, and Copilot Studio agents call flows as tools. Microsoft's FlowAgent plugin lets Claude Code and GitHub Copilot CLI build and debug flows. Zapier, Make and n8n are alternatives to Power Automate. Ditto works alongside your flows, keeps one memory across Power Automate and every app you connect, and acts in them.
| Capability | Ditto | Power Automate's own AICopilot, AI Builder, Copilot Studio | ChatGPT or Claude + Power AutomateFlowAgent plugin, FlowStudio MCP | Automation toolsZapier, Make, n8n | AI agentsIn Slack and Teams |
|---|---|---|---|---|---|
Remembers across sessions, models and toolsiAsk weeks later, on a different model or from Claude, and what your flows did is still there. | ✓Full | –Partial | –Partial | ✗None | –Partial |
Remembers why an approval stalled, and who decidediRun history shows that an approval is pending or rejected. Ditto links the Teams chat or email that explains it. | ✓Full | ✗None | –Partial | ✗None | –Partial |
One memory across Power Automate and every app you connectiWhat Ditto learns from a flow run is there when you ask from Outlook, Slack or a coding agent, and the other way round. | ✓Full | –Partial | –Partial | ✗None | –Partial |
Answers one question from Power Automate and your other appsiChecks the run, the email and the chat at once, while an AI Builder prompt works only from the inputs earlier flow steps pass in. | ✓Full | –Partial | –Partial | ✗None | –Partial |
Acts in Power Automate and your other apps from one requestiOne request resubmits the failed run, drafts the supplier email and posts the update to your finance channel. | ✓Full | –Partial | –Partial | –Partial | ✓Full |
Runs on a scheduleiA Friday digest of stuck approvals. Scheduled flows need someone to build them first; Ditto sets up a scheduled task from a plain request. | ✓Full | ✓Full | –Partial | ✓Full | ✓Full |
Built into Power Automate, nothing to installiCopilot is already in the Power Automate designer. Ditto connects to Power Automate from the Ditto app. | ✗None | ✓Full | –Partial | ✗None | ✗None |
The same memory in ChatGPT, Claude, Cursor and your other AI toolsiMicrosoft's FlowAgent plugin gives Claude Code access to your flows, but each AI tool keeps its own memory. | ✓Full | ✗None | –Partial | –Partial | ✗None |
Pick the model for each task, or bring your own keyiChoose the model for each job from any provider, or use your own API key. | ✓Full | –Partial | –Partial | ✓Full | ✗None |
Read-only until you turn on writingiDitto can read your flows and runs before it can change anything. Turn on writing for Power Automate when you're ready. | ✓Full | –Partial | –Partial | –Partial | –Partial |
See, edit and export what it remembersiOpen what Ditto remembers about a flow or a supplier, correct it, export it or delete it. | ✓Full | –Partial | –Partial | ✗None | ✗None |
Power Automate connects these apps one flow at a time. Ditto brings them into one memory, next to your flows, so you ask in one place instead of checking each app.
Your plan covers capacity and features. Credits pay for variable usage across AI, voice, tool actions and storage beyond your included allowance.
New plan preview. Rollout is in progress; check the offers available in your account before purchasing.
Explore Ditto with no card needed.
Plan includes:
Add a $5 initial deposit for more usage, with no subscription. The full deposit becomes usage credits; checkout adds any tax. Flex checkout asks you to authorize automatic refills: you set a monthly limit, which includes tax, and can turn refills off anytime.
Paid chat connections, parallel reviews and remote control unlock after the deposit settles. Free already includes one Ditto Review at a time.More room for your everyday work.
Plan includes:
Shared capacity and credits for you and your team.
Plan includes:
A custom Ditto build for your business: our team writes the spec, builds it and supports it.
Yes. Ditto keeps a memory of your flows, runs and approvals next to your email, chat and files. Ask weeks later, in the Ditto app, in Slack or from an MCP client, and it answers with sources. It can only read runs Power Automate still stores, which Microsoft keeps for 28 days by default.
Cloud flows and their steps, run history with error messages, approvals, desktop flows, work queues, connections and solutions. It starts read-only, and in a shared space each person gets answers only from what they can already see.
Yes, once you switch writing on for Power Automate. Ditto can create or edit a flow, turn it on or off, resubmit or cancel a run and start a desktop flow. Changes wait for your approval unless you set an action to run on its own. Once a flow is on, it runs in Power Automate on its trigger.
Copilot builds and edits flows from a description, and AI Builder prompts work from the inputs a flow passes in. Ditto keeps one memory across Power Automate and your other apps, so it knows why a flow exists and who is waiting on it. It acts across those apps from one request, and you pick the model.
The new plans are Free, Flex with a $5 initial prepaid deposit and no monthly base fee, Plus at $19/month, and Pro at $97/month. Usage is prepaid with credits. See the pricing page for plan details and rollout availability. Your Microsoft licence is separate and doesn't change.
No. Your flows keep running in Power Automate, on their own triggers, with their run history in Power Automate. Ditto works alongside them: it remembers what they did, explains failures and makes the changes you approve. It isn't a connector or a step inside a flow.
Microsoft's power-automate plugin connects Claude Code and GitHub Copilot CLI to your flows through its FlowAgent MCP server, and third-party servers such as FlowStudio do a similar job. They let one AI tool build and debug flows. Ditto's MCP server gives those tools one memory across Power Automate and your other apps.
Yes. Claude Code can build and debug flows through Microsoft's FlowAgent plugin, and FlowStudio connects ChatGPT and Claude. Connect Ditto over MCP as well and those tools can also recall what your team knows about each flow from email, chat and files. Inside those tools, Ditto supplies memory and context.
Connect Power Automate from the Ditto app with your Microsoft work account. The connection starts read-only, and there's nothing to add to your flows: Ditto isn't a connector or custom connector in the designer. Disconnecting stops Ditto reading Power Automate.
Not for Ditto itself. According to Microsoft, the “When an HTTP request is received” trigger needs a premium licence, and desktop flow runs need attended RPA rights or an unattended add-on. Ditto's pricing is separate from your Microsoft licence.
Yes. Ditto connects to Outlook, SharePoint, Teams, Excel and the rest of Microsoft 365, alongside apps such as Salesforce, Xero and Slack. What it learns in each one joins the same memory as your flows.
No. Creating a flow, turning it on and resubmitting a run wait for your approval. After that the flow runs in Power Automate on its trigger, with its run history kept in Power Automate. Ditto reads those runs afterwards; it doesn't review each one before it happens.
No. Your data is not used to train AI models. Data stored in Power Automate stays under your organisation's Microsoft terms.
Yes. Open any memory to see where it came from, then edit, export or delete it. Disconnecting Power Automate stops Ditto reading it.
Ditto connects Power Automate to every app your team uses, remembers what your flows did and acts when you ask. Start on the free plan, then prepaid usage is available with Flex.
Read-only by defaultNo card to start