To connect Salesforce and NetSuite, you have three options: Oracle's own Salesforce Connector for NetSuite, a MuleSoft Composer flow built in Salesforce, or a Zapier zap. Each one can turn a closed deal into a NetSuite record. Where it stops: Oracle's connector needs a OneWorld account and an admin to run it, a cleared field or an order with many lines can trip up the others, and none of them check that the order matches the deal. AI agents move the deal into an order, check it, and post the order and payment status back on the deal.
What a Salesforce integration with NetSuite has to do
Sales closes the deal in Salesforce. Finance builds the order and the invoice in NetSuite. Without a connection, someone types the deal in twice, and the two drift apart: a price, a product, a ship date.
So a good connection does two things. It turns each closed deal into the right sales order. And it sends back what sales needs: the order status and whether the customer has paid.
Three ways to connect them
One comes from Oracle, one from Salesforce, and one from Zapier.
Oracle's Salesforce Connector
- How it works
- An admin installs Oracle's NetSuite Connector Platform SuiteApp, adds an API-only user in Salesforce, and runs a setup wizard. The connector then syncs the two, starting with your NetSuite items.
- Good for
- NetSuite companies that want Oracle's own tool, set up and kept up by an admin.
- Where it breaks
- It needs a OneWorld NetSuite account, certain features turned on, and a Salesforce edition with API access. Only an Administrator can see its tab. People on a NetSuite forum say it suits standard, simple flows.
A MuleSoft Composer flow
- How it works
- You build a flow in Salesforce with no code. Salesforce's own course shows one: when a deal is closed won and has no NetSuite order number, the flow makes the sales order in NetSuite, then writes the order number back on the deal.
- Good for
- Salesforce teams who want to build and own each step themselves.
- Where it breaks
- MuleSoft's docs say Composer is meant for lighter data and skips empty fields by default. Each flow is one job you build and test, so a full setup is many flows to watch.
A Zapier zap
- How it works
- NetSuite is a Premium app on Zapier. Its templates make NetSuite records from new Salesforce leads, or Salesforce leads and contacts from new NetSuite records.
- Good for
- Simple moves one way, like a new customer in one program showing up in the other.
- Where it breaks
- Each zap is one trigger and one action. Zapier's help says orders with many lines can make the NetSuite trigger fail.
Arkeo agents
- How it works
- Agents read each closed deal in Salesforce, enter the sales order in NetSuite, check the items and prices match the deal, and post the order and payment status back on the deal as a note.
- Good for
- Teams where sales and finance need the same answer, and nobody has the hours to check.
- Where it breaks
- Anything your rules keep for a person, like a price that doesn't match or a large order, goes to your team in one message.
Set up Oracle's Salesforce Connector: the five parts
Oracle's setup page has the full screens. These are the parts, in order.
- 1Check both sides first
Your NetSuite account must be OneWorld with at least one subsidiary. Your Salesforce edition must allow API access; Professional Edition doesn't by default, and the wizard asks which you have.
- 2Turn on the features it needs
In NetSuite, go to Setup > Company > Setup Tasks > Enable Features. Turn on Multiple Units of Measure, Multiple Currencies, Custom Records and Item Options.
- 3Install the SuiteApp and make the Salesforce user
Install the NetSuite Connector Platform SuiteApp, in a sandbox first if you can. In Salesforce, add an API-only user and an External Client App.
- 4
Run the setup wizard
Logged in to NetSuite as an Administrator, follow the wizard. Then set your lookups and page layouts, and give the integration user its permission sets.
- 5
Load your items, then test one deal
Sync your items from NetSuite to Salesforce. Then run one deal through and check the order in NetSuite line by line.
Where the Salesforce NetSuite integration stops
Each tool gets a deal from Salesforce into NetSuite. The work left is between them: checking the order, and telling sales what happened next.
Oracle's connector fits a set shape: a OneWorld account, certain features turned on, and an Administrator to see its tab at all. On a NetSuite community forum, several people who set these up say it works for standard, simple flows, and that custom rules send them to other apps or custom code.
Blank fields and times don't carry the way you expect. MuleSoft's docs say Composer skips empty fields by default, so a value cleared in Salesforce stays in NetSuite. It reads times as UTC, which can move a date by a day.
Orders with many lines are harder. Zapier's help says a NetSuite search that returns one row per line item makes the trigger fail, and changing a field it uses to spot new rows sends the same row through again.
And nothing checks the result. Salesforce's own course on this flow starts from reps building the order in NetSuite and copying the order number back by hand. A connector takes over the copying. Someone still compares the order to the deal and tells sales who has paid.
The agents that do it
Each agent does one job from start to finish in your NetSuite or Salesforce, passing the work between them.
No more typing in wholesale orders.
- Reads orders from emailas they land
- Enters them in NetSuitesame day
- Sends the buyer a confirmationright away
Late orders found before the buyer asks.
- Checks sales orders are packed and shippedevery day
- Finds orders sitting too longsame day
- Tells your ops lead and the buyerright away
Salesforce stays right without anyone typing.
- Logs emails and callsas they happen
- Closes the task when the reply landsright away
- Moves the deal to the right stageper deal
No lead sits with no one on it.
- Reads each new leadas it comes
- Sends it to the right rep by your rulesright away
- Flags leads no one has calledsame day
Questions
Is my customers' information safe?
Yes. Agents work in your own Salesforce and NetSuite and see only what their job needs. Customer details never go into public AI. Agents connect to AI through business-grade connections audited under SOC 2.
Does NetSuite have its own Salesforce integration?
Yes. Oracle makes a Salesforce Connector that runs in the NetSuite Connector Platform. It needs a OneWorld NetSuite account and a Salesforce edition with API access.
Can I build a Salesforce NetSuite integration using the REST API?
Yes, a developer can write it. Your Salesforce edition still needs API access, as Oracle's page notes. After that you own the code, and you fix it each time either program changes.
Should sales see invoices from NetSuite in Salesforce?
Most teams want at least the order status and whether it's paid. With Composer or Zapier, that is another flow you build; agents can post it on the deal.
What does it cost?
You get the price on the call, along with the hours it saves your team.
Sources
- docs.oracle.com: article 2155722791.html
- docs.oracle.com: section 0602041157.html
- docs.mulesoft.com: ms composer netsuite reference
- docs.mulesoft.com: ms composer ms release notes ki
- trailhead.salesforce.com: examine an integration use case 4
- help.zapier.com: Troubleshooting NetSuite on Zapier
- zapier.com: salesforce
- archive.netsuiteprofessionals.com: how does celigo now compare to netsuite connector seems like