Connect Foundry to Oracle NetSuite using the SuiteTalk framework and start syncing data from your NetSuite ERP to Foundry.
| Capability | Status |
|---|---|
| Exploration | 🟢 Generally available |
| Batch syncs | 🟢 Generally available |
| Incremental | 🟢 Generally available |
Learn more about setting up a connector in Foundry.
The NetSuite SuiteTalk source uses token-based authentication (TBA) ↗.
The token-based authentication feature must be enabled on your account. To enable TBA, see the NetSuite documentation ↗.
Access control in NetSuite is configured via the assignment of roles to a user; each role is a collection of permissions that define what tasks the user can perform and what data they can access. We recommend the following configuration for the user that will connect to Foundry:
Create a dedicated role with appropriate permissions.
foundry-role.
Assign the new role to a user.
foundry-role) from the dropdown list, select Add and then Save.To verify that you added the correct permissions, log in as the user you have assigned the new role to, and check that you can view all the data that you expect.
Integration records are used in NetSuite to manage connections to external systems. We recommend the following configuration to connect to Foundry:
foundry-integration.CLIENT ID and CLIENT SECRET. You will need them to configure Foundry.CLIENT ID and CLIENT SECRET will only be displayed the first time you save the integration record. To get new values, you must reset the CLIENT ID and CLIENT SECRET, which invalidates the previous values.
foundry-integration in our example), the user to which you have assigned the newly created role (foundry-role), and the newly created role.
foundry-role) assigned to it.TOKEN ID and TOKEN SECRET. You will need them to configure Foundry.TOKEN ID and TOKEN SECRET will only be displayed the first time you save the token. You will need to create a new token to get a new TOKEN ID and TOKEN SECRET.
Learn more about token management in NetSuite. ↗
The table below lists the domains that the source needs to be able to access in order to run.
If running the connection on a Foundry worker, add corresponding egress policies for each of those domains on port 443.
If those domains are in a different network from Foundry's network, and you are using agent proxy egress policies (preferred) or an agent worker (not recommended), the agent must be able to reach the domain addresses. Additionally, the systems on those domains must be configured to allow connections from the agent. Learn more about agent networking.
| Domain | Required |
|---|---|
<ACCOUNT_ID>.suitetalk.api.netsuite.com | Always. You can find your account ID in the URL when connected to NetSuite. |
webservices.netsuite.com | Always |
| Option | Required? | Description |
|---|---|---|
Account ID | Yes | NetSuite Account ID, found as a prefix in your NetSuite's instance URL |
Client ID | Yes | CLIENT ID copied when creating the foundry-integration |
Client secret | Yes | CLIENT SECRET copied when creating the foundry-integration |
Access token | Yes | TOKEN ID copied when creating the TBA token |
Access token secret | Yes | TOKEN SECRET copied when creating the TBA token |
The NetSuite SuiteTalk source can be explored to discover tables and create new syncs. You can also manually create new syncs from the overview page of the source.