Oracle NetSuite

Provides integration with Oracle NetSuite REST Web Services for metadata-driven record operations and ad-hoc SuiteQL queries.

Revision History

0.0.0.4 - Initial release.
0.0.0.5 - Improved OAuth connection handling.
0.0.0.6 - Improved error message handling.
0.0.0.11 - Corrected Node name.
0.0.0.19 - Updated parameters and templates.
0.0.0.24 - Added Generic SuiteQL Query Template.

Connection

Use this Connection to store your NetSuite account details, OAuth settings, cached metadata, and request timeout settings.

Property	Type	Description
Account ID	String	The NetSuite account ID, e.g. demo123.
Record Types	String	Optional record types to include when you run Acquire Metadata. Enter one record type per line.
Client ID	String	The NetSuite integration client ID.
Client Secret	Masked	The NetSuite integration client secret.
Access Token	Masked	The OAuth access token obtained during authorization.
Refresh Token	Masked	The OAuth refresh token obtained during authorization.
Scope	String	The OAuth scope requested during authorization. The default is rest_webservices.
Timeout (seconds)	Integer	The timeout applied to API calls and metadata acquisition. The default is 30.

Setup Notes

1. Create a NetSuite Integration record with REST Web Services enabled, and then capture the Client ID and Client Secret.
2. Confirm your NetSuite Account ID, e.g. demo123, and make sure REST Web Services are enabled for the account.
3. Configure the OAuth redirect URI in NetSuite, and then complete the Flowgear OAuth flow so the Connection stores Access Token and Refresh Token.
4. Limit the metadata catalog to specific record types in Record Types when you want faster metadata acquisition or narrower template coverage.
5. Use the template picker to choose the required OperationId before invoking the Node.

Methods

The Oracle NetSuite Node separates read operations from create, update, and delete operations. It also adds a built-in Generic SuiteQL Query template to the Query templates.

Query

Retrieves NetSuite resources. The Generic SuiteQL Query template is also available here for ad-hoc SuiteQL statements.

Parameter	Type	Description
Connection	Connection	The NetSuite REST Connection with OAuth credentials and cached metadata.
OperationId	String	The operation identifier selected from the NetSuite metadata catalog.
q	String	Optional SuiteQL statement used only by the Generic SuiteQL Query operation.
Parameters	Object	Optional string values used for route and query parameters. When you use Generic SuiteQL Query, this object also supplies placeholder replacements for values referenced in q.
Items	Array	Optional request body items for query templates that accept a body. Items is not supported for Generic SuiteQL Query.

Return	Type	Description
Response	Array	Streamed response items. Paged NetSuite list responses are emitted one item at a time, and each item includes status, statusMessage, and errorMessage.

Mutate

Creates, updates, or deletes NetSuite resources.

Parameter	Type	Description
Connection	Connection	The NetSuite REST Connection with OAuth credentials and cached metadata.
OperationId	String	The operation identifier selected from the NetSuite metadata catalog.
Parameters	Object	Optional route and query parameter values applied to the request.
Items	Array	Optional request body items. Each input item is serialized and sent as a separate NetSuite request.

Return	Type	Description
Response	Array	Streamed response items. Each item includes status, statusMessage, and errorMessage, and primitive responses are wrapped in value.

Usage Notes

• Only the record types included in cached Metadata are available in templates.
• Run Acquire Metadata again after changing Record Types or when your NetSuite metadata changes.
• The Generic SuiteQL Query template appears in the Query templates and expects the SuiteQL statement in q.
• For Generic SuiteQL Query, add placeholder text directly in q, e.g. @ID, and then supply matching string values in Parameters.
• NetSuite list responses and Generic SuiteQL results are paged automatically. The Node follows the next-page link and emits one item at a time.
• Response objects include status, statusMessage, and errorMessage so you can handle success and failure paths in the Workflow.