Short answer: Drop the "NetSuite → Create NetSuite Customer" 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 |
|---|---|---|---|
Company Name companyName | string | Optional | Required for company customers. e.g. "Acme Inc" |
First Name firstName | string | Optional | Jane |
Last Name lastName | string | Optional | Doe |
Email email | string | Optional | jane@acme.com |
Phone phone | string | Optional | +15551234567 |
Subsidiary Internal ID subsidiary | string | Optional | Internal ID of the subsidiary. Required on OneWorld accounts. |
Customer Type isPerson | options | Optional | — |
External ID externalId | string | Optional | Optional external identifier for cross-system mapping. |
{"companyName": "Acme Inc","firstName": "Jane","lastName": "Doe","email": "jane@acme.com","phone": "+15551234567"}
{"id": "501","email": "jane@acme.com","entityId": "Acme Inc","companyName": "Acme Inc"}
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.