Integrations

Enterprise system integrations

Govern what AI is allowed to change in the systems that hold your real state — SAP and Salesforce through to ServiceNow, Jira, GitHub and Slack.

How a connection works What happens at the boundary

A connector is a ceiling

The permitted-action list is not a menu of what OpsAI can do. It is the outer limit: an action absent from it cannot be authorized by any policy.

Which makes leaving an action off the cheapest control available.

Available

Connected here

Where availability is real

A connector is per-system work, so this page says where each one stands.

A connector holds a credential and knows one system's action vocabulary — that a refund has an amount and a ceiling, that a journal entry belongs to a period. That understanding has to be built, so availability varies and the entries that are not ready stay on the page.

available: Governed today, with the action vocabulary of that system.
in progress: Being built. Partially usable, and the gap is named on the entry.
not yet: Not started. Reachable only through a generic connection, if at all.

Salesforce
Salesforce
available
Record updates, with the field-level scope declared on the connection.
NetSuite
NetSuite
available
Vendor creation and updates. New-payee actions carry a second pair of eyes.
ServiceNow
ServiceNow
available
Ticket and change-request actions, including the ones that trigger downstream automation.
Slack
Slack
available
Outbound messages against approved templates, and co-sign requests for held actions.
Jira
Jira
available
Issue transitions. A status change that releases a deployment is a consequential action.
GitHub
GitHub
available
Writes to a repository, and the search index discovery reads to find undeclared model calls.
Zendesk
Zendesk
available
Ticket closure and customer-facing replies.
Razorpay
Razorpay
available
Refunds and captures. The ceiling is a bound, not a setting in the payment console.
Zoho Books
Zoho Books
available
Journal entries, including the ones that only appear during a period close.
Workday
Workday
available
Supported. Deliberately NOT connected in the sample estate — nothing there may reach employee records.
SAP
SAP
in progress
Document posting and master-data changes. The action vocabulary is large and being worked through module by module.
Microsoft Dynamics
Microsoft Dynamics
not yet
Not started. Reachable today only through a generic HTTP connection, which governs the call but not the action semantics.

IllustrativeAn illustrative catalogue for the OpsAI sample estate. §54: two-letter marks rather than logos, because a logo grid reads as a partnership.

What a connection actually is

Not a channel. A ceiling with a credential behind it.

This is the part most worth understanding, because it changes how you use it. The permitted-action list is evaluated before any policy runs, which makes omission a stronger control than any rule you could write.

Connections in the sample estate

12 systems · 11 connected

Every system in the sample estate: its category, the actions the connection permits, and whether it is connected.
System	Category	Actions permitted	Status
Razorpay	Payments	issue.refund · capture.payment	Connected
RazorpayX	Payouts	initiate.payout	Connected
Zoho Books	Accounting	post.journal_entry	Connected
NetSuite	ERP	create.vendor · update.vendor	Connected
Salesforce	CRM	update.record	Connected
Postgres	Database	adjust.stock · update.row	Connected
Zendesk	Support	close.ticket	Connected
Gmail	Email	send.email	Connected
Slack	Messaging	notify · request_cosign	Connected
Amazon S3	Storage	export.dataset	Connected
Box	Documents	read.contract	Connected
Workday	HR	—	Not connected

Three layers, and each one can only narrow.

The connection
What may ever reach this system. Nothing outside this list can be authorized, regardless of policy or autonomy.
The AI system’s attempts
What this particular system may propose. A subset of the connection, declared at registration.
The bound
Whether this specific instance is allowed — the amount, the payee, the window, the period. Evaluated per action with no model call in the path.

Why Workday is here and unconnected

Workday is available as a connector and deliberately not connected in the sample estate. Nothing there may reach employee records.

Supported and connected are different facts. Collapsing them would turn a working control — a decision somebody made — into a product gap.

Not connected. Nothing an agent does can reach employee records today.

What is worth governing first

The actions that move money or touch a ledger.

These are the ones a bound can refuse on size alone, which makes them the cheapest place to start and the most expensive place to have got wrong. Every one carries a ceiling in the sample estate.

Action templates

in the estate

Carrying a ceiling

refusable on size alone

Systems reached

via a connection

Credentials in your code

grants are derived per action

issue.refundRazorpay: Governed by refund.ceiling, which can refuse it on the amount before anything reaches the system.
post.journal_entryZoho Books: Governed by close.controls, which can refuse it on the amount before anything reaches the system.
initiate.payoutRazorpayX: Governed by payout.dual_control, which can refuse it on the amount before anything reaches the system.

IllustrativeIllustrative actions from the OpsAI sample estate. The policies that govern them.

Where to start

Connect the system that would hurt most, with the shortest action list you can live with.

Not the easiest connector and not the longest list. A connection permitting two actions is a stronger control than one permitting twenty with rules about eighteen of them.

How a connection works The policy register Ask for a connector