Your scenarios keep running in Make. Ditto remembers what they did, next to your orders, email and chat, and answers any question with the sources.
Free plan, no card needed. See pricing for prepaid usage plans.
The delivery-booking scenario has failed since 24 September, when the courier moved postcodes to a new field. Kofi paused it on 25 September, and #10482 is one of 11 orders waiting in Make.
Check overnight runs of the delivery-booking scenario, list orders still without a courier slot, and post them in #ops with each customer's promised date.
Make shows a scenario was paused, not who paused it or why.
Run errors sit in Make. The orders and the fix sit elsewhere.
What each scenario does, to every new starter and every AI chat.
The scenario gets fixed, but the orders it missed never get chased.
Who paused, edited or restarted it, and why, linked to the run, email and thread behind it. Ask weeks later and get the answer.
Shopify, Gmail, Slack, Xero and many more feed one memory, next to your scenarios. Ask once and Ditto checks them all.
Retry the 11 failed delivery bookings in Make, then draft an email to each customer with their new date.
Retries the failed runs, updates the orders and drafts the customer emails, then waits for your OK. Your scenarios keep running in Make.
Use a low-cost model for the daily run check, or connect Claude and Cursor over MCP. Ditto brings the same context every time, so nobody re-explains.
Ditto is for teams whose work spans several apps and several people. If the answer, or the follow-up, lives in more than one place, 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 Make through Make's MCP server. Ditto starts read-only until you turn on writing.
Scenarios, runs, orders 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 runs your scenarios when you approve.
Make AI Agents and Maia build and run automations inside Make. Make's MCP server lets ChatGPT and Claude run your scenarios. Other automation tools run fixed steps. Enterprise search looks across apps. Ditto keeps one memory across Make and every app you connect, and acts from a request.
| Capability | Ditto | Make AI Agents and MaiaBuilt into Make | ChatGPT or Claude + MakeMake MCP server, Make plugin | Other automation toolsZapier, n8n | Enterprise searchGlean, Dust |
|---|---|---|---|---|---|
Remembers across sessions, models and toolsiAsk weeks later, on a different model or from Claude, and the context is still there. | ✓Full | –Partial | –Partial | ✗None | –Partial |
Remembers why each scenario changediAsk why a scenario was paused and get the run, the email and the thread behind it. | ✓Full | –Partial | ✗None | ✗None | –Partial |
Builds its memory on its own, with no data store to designiMake's own guidance is to design a state schema and write it to a data store; Ditto's memory fills itself from every app you connect. | ✓Full | ✗None | ✗None | ✗None | –Partial |
Answers one question from Make and your other apps togetheriChecks runs, orders, email and chat at once, with the source for each part of the answer. | ✓Full | –Partial | –Partial | ✗None | ✓Full |
Acts from one request, without building a scenario firstiAsk for the outcome and Ditto uses each app's own actions, with no trigger or modules to wire first. | ✓Full | –Partial | –Partial | –Partial | –Partial |
Runs your existing Make scenarios from a requestiDitto, Make AI Agents and MCP clients can all run the scenarios you already built. | ✓Full | ✓Full | ✓Full | ✗None | ✗None |
Built into Make, nothing to installiMake AI Agents are available on all Make plans. Ditto connects to Make through Make's MCP server. | ✗None | ✓Full | –Partial | ✗None | ✗None |
The same memory in the Ditto app, Slack and your AI toolsiUse the same memory from the Ditto app, Slack, Claude, Cursor or Codex. | ✓Full | ✗None | –Partial | ✗None | –Partial |
Starts read-only, and you choose what runs on its owniDitto changes nothing in Make until you turn on writing, and each change waits for approval unless you set it to run on its own. | ✓Full | –Partial | –Partial | –Partial | –Partial |
Respects Make permissions in every answeriDitto checks the permissions set in Make before it shares anything, so each person only gets answers about scenarios they can already see. | ✓Full | ✓Full | ✓Full | –Partial | ✓Full |
Pick the model for each task, or bring your own keyiChoose the model for each job from any provider or use your own key; Make AI Agents also take a custom provider on paid plans. | ✓Full | ✓Full | –Partial | ✓Full | ✓Full |
See, edit and export what it remembersiOpen what Ditto remembers, correct it, export it or delete it. | ✓Full | –Partial | –Partial | ✗None | –Partial |
Connect them once. Ditto remembers across all of them, next to the scenarios you already run in Make, not in place of them.
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 scenarios, their runs and failed executions, next to your orders, email and chat. Ask weeks later, in the Ditto app, in Slack or from an MCP client, and it answers with what happened and its sources.
What Make's MCP server exposes: your scenarios and their runs, incomplete executions, connections, webhooks, data stores, teams and organisations. It starts read-only, and it checks the permissions set in Make before it shares anything, so each person gets answers only about scenarios they can already see.
It uses Make's own tools: run a scenario, retry a failed run, edit a scenario, turn it on or off, and update data stores and webhooks. Make says managing scenarios needs a paid Make plan. Changes wait for your approval unless you set an action to run on its own, and a scenario you turn on then runs in Make.
Make AI Agents act inside your scenarios, and they remember a conversation when you give it a Conversation ID. Ditto keeps one memory across Make and your other apps, builds it on its own, works with any model you choose and brings the same memory to Claude and Cursor.
Make says AI Agents are available on all plans, and its MCP server is included in every plan at no extra cost: you pay for the credits your scenarios use. Every scenario Ditto runs uses Make credits too. Ditto starts free, and prepaid usage is available with Flex.
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.
Yes. Connect Ditto over MCP and those tools can search what your scenarios did, next to your other connected apps, and save what you do there. They don't act in Make through Ditto.
Yes. Make is a built-in connector in Claude, and Make has an official plugin for ChatGPT, so both can run and manage your scenarios. Ditto adds a memory across your other apps, actions that wait for your approval, and a choice of model.
Yes. Make AI Agents reason and act inside your scenarios, and Maia by Make builds scenarios and agents from plain language. Ditto works alongside them: it remembers what happened across Make and your other apps, and you pick the model.
Make's MCP server lets AI tools run your active and on-demand scenarios and, on paid plans, view and change scenarios, connections, webhooks, data stores and teams. Ditto connects to Make through it, then keeps what happens in one memory with your other apps.
No. Ditto works alongside Make. Your scenarios keep running there on their triggers and schedules. Ditto reads Make and your other apps into one memory, answers across them and acts when you ask. Keep the scenarios you already run.
Yes, in a shared team space. Ops, support and finance work from the same scenario history, and Ditto checks each person's Make permissions before it answers. Team memory stays when someone leaves, including why each scenario was built.
No. Your memory is not used to train models. Open any memory to see where it came from, then edit, export or delete it. Disconnect Make and Ditto stops reading it.
Ditto connects Make to every app your team uses, remembers what your scenarios 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