46 pre-built, pre-authenticated operations. The bot reads the conversation, picks the right ones, and executes them — without a single HTTP node, bundle, or API credential you have to manage.
Connecting NetSuite to a chatbot used to be a developer project. Skills make it a business task.
The AI node, the credential config, and the 46 skills work together. You only supply the credentials.
Account ID (your NS account number) · Consumer Key (identifies the app — like a Client ID) · Consumer Secret (like a Client Secret) · Token ID (which NS user/role this acts as) · Token Secret (proves the token). Velaro encrypts all five server-side. They never appear in a workflow definition, a log, or the bot's prompt.
When a visitor says "where's my shipment?", the AI node gets the full conversation context — including the email they entered in prechat. It selects netsuite_search_orders and passes that email as the lookup key. No routing rule. No workflow branch.
The skill signs the NetSuite REST request using your stored credentials, routes to the correct record type, validates field names against NetSuite's metadata, and returns a structured result the bot reads back to the customer.
Every NetSuite lookup starts from data the conversation already collected. The visitor's email, name, and phone from prechat flow silently into every skill call as the lookup key. Your customer never types their account number into a chat window.
That's the difference between a chatbot that feels like a search form and one that feels like an agent who already pulled up the account.
No workflow authoring. Turn on the integration and every skill below is available to the AI immediately.
Every other approach requires you to be a NetSuite developer. Skills don't.
| Velaro AI Skills | HTTP Nodes | NetSuite Bundles | Raw MCP | |
|---|---|---|---|---|
| API knowledge required | ✓ None | ✗ Must know REST endpoints | ~ Partial (install only) | ✗ Must build tool server |
| OAuth setup | ✓ Paste 5 values once | ✗ Construct signature in every node | ~ Bundle handles it | ✗ You implement signing |
| Operations available | ✓ 46 out of the box | ✗ You build each one | ~ Fixed 5-10 in bundle | ✗ You define each tool |
| Skill selection | ✓ LLM reads conversation | ✗ You write every if/then branch | ✗ Fixed action trigger | ~ LLM selects if wired correctly |
| Customer identity threading | ✓ Prechat email auto-threaded | ✗ You pass vars manually | ✗ Not supported | ✗ You implement context passing |
| Field validation | ✓ Discover Properties UI | ✗ Typos break silently | ~ Bundle fields only | ✗ You validate yourself |
| Multi-step composition | ✓ LLM chains dynamically | ✗ Requires branching workflow | ✗ Not supported | ~ If tools are wired |
| Custom SuiteScript | ✓ Restlet skill included | ✓ Fully custom | ✗ Not supported | ✓ Custom only |
Note on MCP: MCP is the protocol layer that connects the LLM to tool implementations — it is not an alternative to Skills. Velaro's skills are pre-built, pre-authenticated named operations that run over MCP. Building raw MCP yourself means building and hosting the tool server, writing the OAuth signing, and defining every operation from scratch — the same work HTTP nodes required, now in a different format.
This is not a different wrapper on the same approach. The architecture behind Velaro's NetSuite skills represents a novel method for executing ERP operations from live conversations — one that removes every step a developer used to own.
These four properties together — dynamic composition, implicit identity threading, pre-authenticated registry, and credential isolation — define a method that does not exist in bundle-based, HTTP-node-based, or raw-MCP-based architectures.
Paste your 5 OAuth credentials. All 46 skills activate immediately. No developer, no bundle install, no HTTP node.
BFN-certified NetSuite partner since 2008. Listed on SuiteApp.com.