[ Salesforce / ERP visibility ]

Salesforce and NetSuite, in step both ways

engini keeps Salesforce accounts and NetSuite customers in step, and writes NetSuite invoices, balances and payment status to the Salesforce account. Reps can also ask Claude or ChatGPT what a customer owes and bought, and the agent reads both systems live, under the controls you set.

SalesforceNetSuiteSAP S/4HANAClaude
Read the Salesforce guide →
Two directions, one connection each
  1. Salesforce logo
    Account updated in Salesforcerecord trigger, every 15 min
  2. NetSuite logo
    Customer upserted in NetSuitematched on the Salesforce account id
  3. NetSuite logo
    Invoice updated in NetSuiterecord trigger, every 15 min
  4. Salesforce logo
    Balance and invoice on the accountcustom fields or an invoice object
Illustration of the flow on this page, not a product screen.
What it does
Accounts both ways; invoices, balances and payments into Salesforce
Systems
Salesforce, NetSuite (or SAP S/4HANA), Claude or ChatGPT
Built with
Workflows on Salesforce and NetSuite triggers; an MCP server for questions
Your control
You decide which system owns which field
[ 01 / The problem ]

Sales sees the deal. Finance sees the money.

Most Salesforce and NetSuite integrations start with orders: a won deal becomes a sales order. The trouble starts when the business wants more, such as order status, invoices and payments flowing back to Salesforce, and accounts kept in step both ways. Celigo describes how custom integrations become hard to maintain at exactly that point.

The cost is visible in every account meeting: a rep calls a customer who is 60 days overdue without knowing it, finance updates a billing address that sales overwrites the next day, and nobody is sure which system is right.

Where two-way sync breaks

  • No agreed owner per field, so updates ping-pong between systems.
  • NetSuite invoices and balances never reach the Salesforce account.
  • Duplicate customers created from slightly different names.
  • Reps message finance to ask what a customer owes.

How engini keeps them in step

Every engini integration runs both ways, so this is one setup with a workflow in each direction. Account changes in Salesforce, checked as often as every 15 minutes, upsert the NetSuite customer, matched on the Salesforce account id. Invoice and payment changes in NetSuite, checked as often as every 15 minutes, update balance and status on the Salesforce account, in custom fields or a custom invoice object, since engini reads each org’s own custom objects and fields.

You write down which system owns which field once, and the workflows follow it. An AI agent step can handle the judgment calls, such as deciding whether two customers are the same company. For questions, reps add an engini MCP server to Claude or ChatGPT and ask what a customer owes and bought; the agent reads both systems live. The same pattern works with SAP S/4HANA, with SAP changes read on a schedule.

[ 02 / How it works ]

One owner per field, a flow in each direction

01 / Decide

Who owns what

Agree which system owns each field: for example Salesforce owns account name and owner, NetSuite owns billing terms, balance and invoices.

02 / Out

Salesforce to NetSuite

Account created or updated in Salesforce upserts the NetSuite customer with the fields Salesforce owns.

03 / Back

NetSuite to Salesforce

Invoice and payment changes in NetSuite update balance, last invoice and payment status on the Salesforce account.

04 / Ask

Questions, answered live

Reps ask Claude or ChatGPT about a customer through an engini MCP server that reads both systems, read only.

[ 03 / What the agent reads and writes ]

What the workflows read and write

SystemRecordsAccess
SalesforceAccount (standard and custom fields), custom invoice objectReadUpdate
NetSuiteCustomerReadUpsert
NetSuiteInvoice, Customer PaymentRead
Claude or ChatGPTRead-only questions across both systems, over MCPRead
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the Salesforce logo, the engini mark and the NetSuite logo joined by a thin line, labeled both ways: account, customer, balance

Editorial image: two systems, both directions.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: when a NetSuite invoice is created or updated, find the Salesforce account whose NetSuite customer id matches the invoice customer, and update its fields Open_Balance__c and Last_Invoice_Status__c with the customer's current open balance and this invoice's status.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect Salesforce, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can we see NetSuite invoices and balances on the Salesforce account?

Yes. A workflow on NetSuite invoice and payment changes, checked as often as every 15 minutes, writes balance, last invoice and payment status to the Salesforce account, in custom fields or a custom object.

Which system owns customer data?

You decide per field. A common split: Salesforce owns name, owner and segment; NetSuite owns billing terms, balance and invoices. The workflows write only the fields each side owns.

Can a rep ask an AI agent about a customer’s invoices?

Yes. Add an engini MCP server with read-only Salesforce and NetSuite tools to Claude or ChatGPT, and reps can ask what a customer owes, bought or was last invoiced.

Does it need custom objects in Salesforce?

Not necessarily. A few custom fields on the account are enough for balance and status. A custom invoice object works too if you want every invoice listed; engini reads each org’s custom objects and fields.

Does it work with SAP S/4HANA instead of NetSuite?

Yes. The same pattern works with SAP’s business partner and billing data over OData. engini has no SAP triggers, so SAP changes are read on a schedule.

How is this different from a prebuilt connector?

You own the field rules and can change them in Workflow Studio, an AI agent can handle judgment calls such as duplicates, and the same connections serve reps’ assistants and your other agents.