You can import user attributes and events from NetSuite ERP into Insider One through standard import channels: the Upsert User Data API for ongoing profile and event updates, FTP/SFTP for scheduled file imports, or Amazon S3 for automated file imports through AWS.
This guide explains how to prepare NetSuite data for these channels and configure the Insider One side of the integration. Your team or integration provider builds and operates the process that extracts data from NetSuite, maps it to the required format, and delivers it to the selected channel.
For values needed at a specific point in a journey, you can also use Architect's Call an API element to request data from an API endpoint backed by your NetSuite integration.
This guide describes an integration through Insider One's standard APIs and file import channels. It does not describe a native NetSuite connector or a direct connection to NetSuite tables.
Essentials before integration
Before you begin, ensure the following prerequisites are met:
You have access to retrieve or export the required data from NetSuite through a method supported by your NetSuite environment.
Your team or integration provider can prepare API payloads or publish export files to the selected destination.
You have identified the user identifiers, profile attributes, and events you want to send.
You have defined how NetSuite source fields map to Insider One identifiers, attributes, events, and event parameters.
To configure FTP/SFTP or Amazon S3 source integrations in InOne, you have an Administrator or Editor with PII access role. To generate an API key for the Upsert User Data API, you have an Administrator role.
Prepare API payloads for the Upsert User Data API, CSV or TSV files for FTP/SFTP, or CSV or JSONL files for Amazon S3. NetSuite records must be transformed into the format required by the selected import channel before they are sent to Insider One.
Choose your import channel
Channel | When to use it | How it works |
|---|---|---|
Ongoing updates to user profiles and events | Your integration job retrieves NetSuite data, maps it to API payloads, and sends requests to Insider One. | |
Scheduled bulk file imports | Your integration job publishes CSV or TSV files to your file server. InOne reads the files on the configured schedule. | |
Batch imports when your data pipeline uses AWS | Your integration job uploads CSV or JSONL files to your S3 bucket. Insider One imports new files through the configured notification flow. |
Import channel 1: Upsert User Data API
The Upsert User Data API sends user attributes and events to Insider One. If a profile exists for the identifier you send, the API updates it. If no matching profile exists, it creates one.
Use this channel to map relevant NetSuite customer data to user attributes and transaction data to user events. For example, you could send a customer field as a profile attribute or represent a completed purchase as an event, depending on your data plan.
Set it up
Plan the user data you will send and get the plan approved by the Insider One team. Use the Upsert User Data API Integration Wizard to generate an API key, configure headers, and prepare payloads.
Build an integration job that retrieves the required NetSuite records through your chosen extraction method.
Transform the records into the required API payload. Place user identifiers under the
identifiersobject and use one identifier per user object where possible.Test the mapping with a small sample and review the API responses.
Run the integration job at the frequency your use case requires.
For payload parameters, limits, and error handling, see Upsert User Data. For guided setup, see the Upsert User Data API Integration Wizard.
Import channel 2: FTP/SFTP
The FTP/SFTP integration allows InOne to read CSV or TSV files from your file server on a schedule and import their data into user profiles and events. FTP, FTPS, and SFTP are supported.
Your integration process is responsible for extracting NetSuite data and publishing the formatted files. The Insider One integration reads those files from the configured server, not directly from NetSuite.
Set it up
Extract the required NetSuite data and transform it into CSV or TSV files that meet the import requirements.
Publish the files to your FTP, FTPS, or SFTP server.
In InOne, navigate to InOne > Components > Integrations > External Integrations, select FTP/SFTP, and enter your server connection details.
Configure the file settings and map user identifiers, attributes, and events.
Set the import schedule to match when your integration process makes the files available.
For protocol selection, credentials, file requirements, and data mapping, see Import Data from FTP/SFTP to InOne.
Import channel 3: Amazon S3
If your data pipeline uses AWS, you can publish NetSuite-derived data to an Amazon S3 bucket you own. Insider One's Amazon S3 integration supports CSV and JSONL files containing user attributes and events, including purchase data.
Your integration process prepares and uploads the files. Insider One reads the resulting files from S3 rather than retrieving records directly from NetSuite.
Set it up
Extract the required NetSuite data and transform it into CSV or JSONL files that meet the import requirements.
In InOne, navigate to InOne > Components > Integrations > External Integrations and create an Amazon S3 source integration.
Authorize Insider One to read from your bucket and configure the required bucket, path, and data mappings.
Configure an Amazon SQS queue for new-file notifications as described in the integration guide.
Publish export files to the configured location so that new-file notifications can trigger imports.
For AWS authorization, notification setup, file requirements, and data mapping, see Import Data from Amazon S3.
Use NetSuite data in real time during journeys
When a journey needs a value at a specific step, use Architect's Call an API element to request it from an endpoint that your integration exposes for NetSuite-backed data.
For example, you could expose an endpoint that returns a customer's current order status from NetSuite. This is a suggested integration pattern, not a preconfigured NetSuite action. Your endpoint determines how the data is retrieved and how current the returned value is.
Set it up
Prepare an API endpoint that retrieves the required NetSuite-backed data and returns the values needed by the journey.
Configure a Call an API element with the endpoint, request details, and the user identifier your endpoint requires.
Configure response variables and data types according to the Call an API data-fetching guide.
Use the returned values in message content, save a value through Update User Attribute, or branch the journey with Check API Response.
Test the request and response mapping before using the lookup in a live journey.
Response variables belong to the journey that fetched them and are deleted when the user leaves it. To retain a returned value on the user profile, explicitly configure a user attribute update. Use the standard import channels for bulk profile and event imports.
For setup, supported response formats, and use cases, see Architect Channel: Fetch Data through Call an API.