NetSuite ERP connector

Create and update purchase orders, bills, vendors and journal entries

ERP and accountingProvided by Oracle NetSuiteVendor-specific

Authentication

Vendor-specific

The vendor uses a login scheme of its own. The connector handles session creation, renewal and expiry internally.

Setup steps depend on the vendor. The connector setup screen lists exactly what to supply.

Credentials are held in the platform credential vault. Agents never see them.
Every call runs as a step in a versioned WorkStream Playbook, so the rules that apply are the rules that were published.
Actions that cross a policy threshold stop at a tollgate and wait for the named approver.
Each call is written to the Execution Ledger with the inputs, the result and the Playbook version in force.

1
Credential resolved
Vendor-specific credential released from the vault to the connector runtime. The step never sees the secret.
2
Action called
A WorkStream step called NetSuite ERP with the inputs recorded on the step, under the Playbook version in force.
3
Policy evaluated
Thresholds on the step were checked. Anything over the limit stops at a tollgate and waits for the named approver.
4
Result written
The response from NetSuite ERP, the timing and the Playbook version were written to the Execution Ledger.

Systems of record for ledgers, purchase orders, expenses and month-end close.

Read and post journal entries, bills, purchase orders and vendors

Acumatica

Access corporate card transactions, expenses and users

17 actions

Read and update parts, orders, jobs and supplier records

Epicor

Create and retrieve expense reports, policies and receipts

15 actions

Read and post financials, purchase orders and asset maintenance records

IFS

Work with finance, supply chain and manufacturing records in CloudSuite

Infor

Connectors only matter inside a WorkStream. The product tour walks a request from intake through a tollgate to a recorded result.