Launching today

MokuBot

Launching today

The AI agent that actually does the work in NetSuite

5 followers

The AI agent that actually does the work in NetSuite

5 followers

Visit website

Most AI tools generate output you still have to act on. MokuBot is an agent - it executes. Write SuiteQL, build saved searches, workflows and live dashboards, create records in bulk, generate and deploy SuiteScript, diagnose failed scripts - all from plain English. Runs in a Chrome side panel on your existing NetSuite session. No setup, no API keys. Read-only by default with granular controls. Tasks that take a developer an hour take two minutes.

Free Options

Launch tags:Chrome Extensions•Productivity•Developer Tools

Launch Team / Built With

Viktor.comAn AI coworker that actually does the work

Promoted

Maker

📌

Hey Product Hunt 👋 I've spent years working inside NetSuite, and one thing always drove me nuts: the data is all there, but it's locked behind menus, internal IDs, and SuiteScript boilerplate. Simple things take an hour. So we built MokuBot. The key thing: it's not a chatbot that tells you what to do - it's an agent that does it. It chains tool calls on its own: queries metadata, runs the API, reads the result, corrects course, reports back. Ask "why did my scheduled script fail last night?" and it digs through execution logs, reads the source, and hands you a diagnosis. It lives in a Chrome side panel and uses your existing NetSuite session and permissions - no setup, no API keys, no admin ticket. If you can see it in NetSuite, MokuBot can work with it. It's read-only by default, and you enable exactly the write capabilities you want. Your chats and dashboards sync to your own Google Drive, not our servers. Devs: there's an MCP bridge, so you can drive NetSuite from Claude Code or Claude Desktop without leaving your editor. What's next: Salesforce support is close. But the part we're most excited about is what comes after - one agent that works across both systems at once. Right now your ERP and your CRM don't talk, and the person stuck reconciling them is you. Imagine asking "which closed-won opportunities from last quarter never turned into an invoice?" and getting the answer, without exporting a single CSV. MokuBot started as an internal tool to save our own team time. It saved hours a week, so we're sharing it. I'm around all day - ask me anything, and I'd genuinely love to hear what breaks. Which system should we connect after Salesforce?

Report

23h ago

How does it handle permissions when it needs to write data, do I just toggle a switch in the side panel or is there a longer approval workflow involved?

Report

19m ago

Maker

Hi @tlinbyktlm4v1 !

It's layered, not a single toggle:

Read-only by default. Every connected account starts this way. MokuBot can look up records, run searches, and navigate, but can't change anything until you allow it.
Granular write toggles. You enable writes per capability: records, scripts, saved searches, custom records, role management, deletes, UI actions. Deletes are separate, so you can permit edits without risking a delete.
Per-account policy. Each NetSuite account has its own settings. Keep Production read-only while a Sandbox is fully open.
Approval before each action. Even with writes enabled, every write triggers an approval card showing the exact operation and data. You approve or reject before it runs.
Optional auto-approve mode. For trusted, repetitive work, you can turn off the per-action prompts and let it run within the capabilities you enabled. Off by default.
Role permissions still apply. MokuBot's access is also capped by your NetSuite role. Even with writes and auto-approve enabled, it can't do anything your role doesn't already permit.

So it scales from fully hands-off to click-to-confirm to full autonomy, and you set the level per account.

More on the architecture here: https://mokuhub.com/mokubot-netsuite/security

Thank you for the interest in our product!

Report

1m ago

Hi @tlinbyktlm4v1 !

It's layered, not a single toggle:

Read-only by default. Every connected account starts this way. MokuBot can look up records, run searches, and navigate, but can't change anything until you allow it.
Granular write toggles. You enable writes per capability: records, scripts, saved searches, custom records, role management, deletes, UI actions. Deletes are separate, so you can permit edits without risking a delete.
Per-account policy. Each NetSuite account has its own settings. Keep Production read-only while a Sandbox is fully open.
Approval before each action. Even with writes enabled, every write triggers an approval card showing the exact operation and data. You approve or reject before it runs.
Optional auto-approve mode. For trusted, repetitive work, you can turn off the per-action prompts and let it run within the capabilities you enabled. Off by default.
Role permissions still apply. MokuBot's access is also capped by your NetSuite role. Even with writes and auto-approve enabled, it can't do anything your role doesn't already permit.

So it scales from fully hands-off to click-to-confirm to full autonomy, and you set the level per account.

More on the architecture here: https://mokuhub.com/mokubot-netsuite/security

Thank you for the interest in our product!