/build-netsuite-automation

name: build-netsuite-automation
allowed-tools: AskUserQuestion, Read, Write(./netsuite-recipe.md), Write(./*.js), Glob, WebFetch(domain:docs.oracle.com), mcp__memorylane__search_context, mcp__memorylane__get_activity_details, mcp__memorylane__get_db_path, mcp__plugin_memorylane_memorylane__search_activity, mcp__plugin_memorylane_memorylane__get_activity_details, mcp__plugin_memorylane_memorylane__list_organizations, mcp__plugin_memorylane_memorylane__list_teams, mcp__plugin_memorylane_memorylane__list_devices
description: >
  (BETA) Turn one process from a MemoryLane analysis, report or screen recording into a
  simple NetSuite automation (SuiteFlow, plus a script only where needed), with a
  short recipe to build, test and switch it on. One happy path, fewest steps.
  Use after analyze-processes.

Process to NetSuite (BETA)

Takes one process a team does by hand in NetSuite and gets a first version running inside NetSuite.

Bar is 80/20. One path, happy path only, fewest steps that work. Odd cases stay with a person. The team improves it from there.

Every record type, field, list, role and approver comes from the material or the user. Never assume a feature, custom field or SuiteApp the material does not show.

Done means

The user holds a short recipe to build the automation, test it on one made-up record, and switch it on. Unless the process should not be automated, every run ends with that, in the same session. If something is missing, put a `FILL IN` placeholder and say who can supply it.

Keep it simple

Simple is the goal. A small automation the team understands beats a safe one nobody uses.

• **One safety net: Testing status.** A NetSuite automation set to **Testing** starts only for its owner, so real work is untouched until it is set to **Released**. Do not add go-live switches, re-checks, custom logs, alerts or timeout paths on top. NetSuite's workflow history and script error emails already cover that.
• **A person check only where a person decides today** (approves, judges, signs off money). Use the record's built-in approval if it has one. If nobody decides today, add no check.
• **Two endings.** Done, or left alone (the record does not fit the rule, so the automation does nothing and the team handles it as today). Nothing else.
• **Fewest steps.** Before handing over, try to remove each step. If the process still works without it, remove it.

How to talk to the user

The user is not technical.

• Very plain words. Short sentences.
• Say "automation" not SuiteFlow workflow, "script" not SuiteScript, "list" not saved search. Give the NetSuite name once in brackets, then the plain word.
• Steps as a numbered list, one action each, with the exact menu path (for example **Customization > Workflow > Workflows > New**) and what they should see after.
• No intros, no recaps. Questions come with choices, your pick first.
• Say plainly what you know, what you guessed, and what is missing.

Rules

1. **Material first, then ask.** Ask questions only at Step 2 and Step 4, up to four per ask. Waiting for an upload or a connection is fine. 2. **No personal data in any output.** Use record types, field IDs and list names. Never copy names, emails or values from real records. Same strip and keep lists as `analyze-processes` principle 9. 3. **Never ask for passwords, tokens or keys in chat.** 4. **The NetSuite connection only reads** (field IDs, lists, record shapes). Never create or change records with it. It cannot build the automation; the user copies it into NetSuite from the recipe.

Step 1. Read everything (no questions yet)

Use what is there, in this order:

1. A `process-analysis*.md` file from `analyze-processes` (glob for it; on multi-person runs there is one per role, so use the one with this process): `steps`, `decision_points`, `common_path`, `what_varies`, `automation`, `reconciliation`. 2. A MemoryLane report the user points to. 3. The user's description, a how-to doc, or a screen recording.

Also:

• **Captured data**, if MemoryLane tools are here (`${CLAUDE_PLUGIN_ROOT}/references/data-sources.md` has the local and remote tool names): `get_activity_details` on the evidence IDs, `search_context` for more runs. NetSuite page addresses show the record type (`/app/accounting/transactions/vendbill.nl`).
• **Recordings:** save one picture every 3 to 5 seconds with ffmpeg (it asks for approval) and read them in order, skipping repeats (about 60 max). The transcript gives the rule and the why. If you cannot run code here, ask for screenshots of the key screens.
• **NetSuite connection:** check this session's tools for NetSuite (`ns_` tools). If there, look up field IDs, the list the work starts from, and status values.

For each step note: record type, fields read, fields changed (with IDs), and what "finished" looks like on the record.

If the analysis says not to automate this, say why in two lines and offer the next best process.

Step 2. Stop one. Choose

One `AskUserQuestion`. Skip anything already answered.

1. **Which process**, if not given. 2. **Which path.** The types of case this process handles. Recommend the most common simple one first, with run counts if the data has them. 3. **Anything else to look at?** Only if the material is thin. "No, carry on" / "A how-to doc" / "A screen recording". 4. **NetSuite connection**, only if not connected. "Connect NetSuite to Claude now (Recommended)" / "I'll copy the automation into NetSuite myself from the recipe".

If they pick a recording, ask for the MP4 file and the transcript (a link will not work), then wait for the upload.

If they pick connect, tell them (check the steps against Oracle's current "NetSuite AI Connector Service" guide first):

1. A NetSuite admin installs the **MCP Standard Tools** SuiteApp. 2. In Claude, add a custom connector with the address Oracle gives for your account. 3. Sign in to NetSuite with a role that can see this process and has the **MCP Server Connection** permi