NetSuite
NetSuite ERP records into your workflow
NetSuite is Oracle's ERP, the back-office system that runs financials, supply chain, and order-to-cash for many mid-market and enterprise companies. Tiny Command exposes it as an action-only surface today (NetSuite's push event system, SuiteAlerts, requires per-record-type config and we're shipping native trigger support in the next release). Nine actions cover the customer, invoice, and order surface: Create Customer, Search Customers, Get Customer, Create Invoice, Get Invoice, Search Invoices, Create Sales Order, List Items, and the related read endpoints. The integration uses NetSuite's OAuth 1.0a with token-based authentication, your NetSuite admin generates consumer key/secret + token/secret pairs scoped to the appropriate role. Common patterns: a Stripe Subscription Created creates the matching NetSuite Customer record and a Sales Order with the subscription line items; or a Shopify Order Created syncs into NetSuite as a Sales Order so the finance team sees revenue in their system of record without manual entry.
Do anything NetSuite can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create NetSuite Customer | Creates a customer record in NetSuite ERP with name, addresses, payment terms. For "new account in CRM → provision in ERP for invoicing" workflows. |
| Create NetSuite Invoice | Creates an invoice tied to a customer with line items, terms, due date. For "external billing system → push to NetSuite for financial consolidation" workflows. |
| Create NetSuite Sales Order | Creates a sales order with customer, items, ship-to address. The standard hook for "e-commerce order → push to NetSuite for fulfilment and finance" workflows. |
| Get NetSuite Customer | Returns a customer by internal ID with all fields including custom fields. The standard lookup for enrichment or validation workflows. |
| Get NetSuite Invoice | Returns an invoice by internal ID with line items, totals, payment status. For revenue-reporting workflows or for sync to other accounting systems. |
| List NetSuite Items | Returns the inventory items in NetSuite. For sync to e-commerce storefronts or for "audit which SKUs we have" inventory workflows. |
| Search NetSuite Customers | Lookup by email, name, or custom field. The standard "find before update" pattern for upsert workflows. |
| Search NetSuite Invoices | Filter invoices by customer, status, date range. For accounts-receivable reporting workflows. |
| Upsert NetSuite Customer | Creates or updates a customer based on external ID. For sync workflows that maintain NetSuite as the financial-master record with CRM as the originating source. |
Pre-built NetSuite workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect NetSuite once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every NetSuite field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the NetSuite integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect NetSuite to Tiny Command?
What NetSuite triggers does Tiny Command support?
What NetSuite actions can I run from a workflow?
Is the NetSuite integration real-time?
Do I need to write code to use NetSuite with Tiny Command?
How much does the NetSuite integration cost?
More payments apps people connect.
Same category as NetSuite, ordered by how often teams pair them. Hover the carousel to pause.
Do more with NetSuite.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
