Short answer: Drop the "NetSuite → Create NetSuite Sales Order" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Customer Internal ID entity | string | Required | 501 |
Transaction Date tranDate | string | Optional | 2026-01-15 |
Memo memo | string | Optional | — |
Line Items items | array | Required | Array of {item: <internal_id>, quantity, rate}. e.g. [{"item": "42", "quantity": 2, "rate": 99.00}] |
Subsidiary Internal ID subsidiary | string | Optional | Required on OneWorld accounts. |
{"entity": "501","tranDate": "2026-01-15","memo": "{{trigger.memo}}","items": "{{trigger.items}}","subsidiary": "{{trigger.subsidiary}}"}
{"id": "9001","total": 198,"status": "Pending Approval","tranId": "SO1042"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.