This article describes the actions available when you connect NetSuite to HappyFox Workflows, and lists the ERP customer management operations you can automate with this integration.
Triggers
The NetSuite integration does not provide triggers. Workflows that include NetSuite actions are started by a HappyFox Help Desk trigger or another connected app.
Actions
| Action | What it does |
|---|---|
| Create Customer | Creates a new customer record in NetSuite using contact and company details from the workflow. |
| Update Customer | Updates the fields of an existing NetSuite customer record. |
Actions
Each action below lists the fields you configure, along with whether each field is required.
Note: Every NetSuite action requires a valid NetSuite OAuth access token and NetSuite account ID. These are configured once at the integration/connector level in your Apps settings — not per action.
Validation note legend
| Term | Meaning |
|---|---|
| Required | The action cannot run without this value. |
| Optional | Can be left blank; the action still runs. At least one optional update field must be provided where noted. |
| Text | A plain string of characters. |
| ID | An internal NetSuite numeric identifier. |
Create Customer
Creates a new customer record in NetSuite with a company name, contact details, and an entity status. On success, returns the new customer's NetSuite internal ID and the record location URL. The action fails if the company name, email, phone, or entity status are missing.
| Field | Description | Validation |
|---|---|---|
| Company Name | The name of the company to create as a customer in NetSuite. | Required · Text |
| The primary email address for the customer. | Required · Text | |
| Phone | The phone number for the customer. | Required · Text |
| Entity Status ID | The internal NetSuite ID of the customer's entity status (for example, prospect, qualified lead, customer). Select from the available status options in your NetSuite account. | Required · ID |
Update Customer
Updates the contact details or entity status of an existing NetSuite customer record, identified by its internal ID. Only the fields you supply are changed — any field left blank is left unchanged on the record.
| Field | Description | Validation |
|---|---|---|
| Customer ID | The NetSuite internal ID of the customer record to update. | Required · ID |
| The new primary email address for the customer. | Optional (at least one of Email, Phone, or Entity Status ID) · Text | |
| Phone | The new phone number for the customer. | Optional (at least one of Email, Phone, or Entity Status ID) · Text |
| Entity Status ID | The internal NetSuite ID of the new entity status to set on the customer. | Optional (at least one of Email, Phone, or Entity Status ID) · ID |
Returns the customer ID and a confirmation message on success.
Use cases
Create a NetSuite customer when a new contact raises a ticket: When a ticket is created by a contact who does not yet have a customer record in NetSuite, automatically create one using the contact's name, email, and company details from the ticket — keeping your ERP current without requiring the finance or operations team to manually add the record.
Update a NetSuite customer record when ticket data reveals changes: When a ticket contact provides updated company information — such as a new billing address, phone number, or company name — automatically update the corresponding NetSuite customer record, preventing data drift between the helpdesk and ERP without a manual update cycle.
Sync new enterprise customers to NetSuite on ticket creation: When a ticket is received from a new enterprise or business contact not yet in NetSuite, create a customer record as part of the ticket intake workflow — so finance and account management have an ERP record from the first interaction, without waiting for a manual handoff from support.
Keep NetSuite customer status aligned with support outcomes: When a ticket resolution indicates a change in a customer's status — such as a churn risk flag, a plan upgrade, or a billing change — update the relevant fields on the customer's NetSuite record as part of the workflow, so the ERP reflects the outcome without a separate manual step.