240+ connectors. Opero reads your stack, doesn't replace it.

Every integration vendor will tell you they connect to your stack. What that usually means: a Zapier listing for a handful of systems, a middleware subscription for the ones that matter, and a professional-services engagement for anything serious. The connectors that actually work in production are the ones named below — built against real production APIs, tested against real data schemas, deployed in live operations.

What it actually does

The design principle is simple: Opero lives inside the tools the team already uses. No new application to log into. No data migration to run before going live.

In practice: the knowledge agent reads manuals and service bulletins from SharePoint; the workflow agent writes work orders into ServiceNow or IBM Maximo; the voice agent routes calls through Twilio or Vonage and reads part availability from SAP; the parts module pulls SKUs and pricing from IFS or Microsoft Dynamics 365. Each capability consumes the systems already in place. The connector is the integration layer; the agent is what makes it useful.

Read access is the default posture for every system. Write access — creating a ticket, committing a parts order, updating a record — is granted explicitly, per system, per action type. That distinction matters when an auditor or an IT security team asks what the agent can do unsanctioned. The answer is: read only, unless the team decided otherwise and the log shows when.

The connectors that exist today

ERP. SAP S/4HANA and SAP ECC (parts and inventory reads, purchase-order writes where granted), IFS Applications (work orders, asset register, parts), Microsoft Dynamics 365 (field service, finance, supply chain), Infor M3 (parts and procurement).

FSM and field service. ServiceNow (ticket creation, work-order updates, asset lookups), IBM Maximo (asset management, PM scheduling, work-order writes), Salesforce Field Service (case creation, resource scheduling).

CRM. HubSpot (contact and deal reads, activity writes), Salesforce (account and opportunity reads, case creation).

Telephony. Twilio (inbound and outbound calling, SMS), Vonage (inbound routing and SIP), regional PSTN gateways on request.

Document management. SharePoint and OneDrive (document reads and metadata indexing), S3-compatible object stores (corpus ingest for air-gapped deployments).

Identity. Azure AD / Entra ID and Okta (SSO and SCIM provisioning), Google Workspace (SSO). Role and group claims from the identity provider flow through to document-level access-control lists without a separate configuration step.

What you control

Write access is scoped per system and per role — the FSM connector can be granted work-order creation rights for senior technicians and read-only rights for field staff, with no shared write token. Every outbound write carries an audit record: the action, the calling agent, the user whose session triggered it, and the timestamp. That log is not configurable; it exists for every write, because regulated operations and high-value transactions require it.

On-prem and air-gapped deployments inherit the same connector set as cloud deployments. The connectors run inside the customer’s environment; no data transits an external network. Behaviour is identical; the deployment boundary moves inward.

When the connector you need does not exist

Custom connectors are built per company against your specific system and schema. The typical timeline is two to four weeks, depending on API availability and schema complexity. Pricing is handled in the commercial conversation — there is no per-connector fee published because the build scope varies.

Where to look next

• Workflows — what these connectors enable when the agent is running a multi-step process: triage, scheduling, PM, parts procurement.
• Knowledge Agent — how the document-management connectors feed a grounded retrieval system that technicians actually use.
• Operations use case — how ops managers and IT leads frame the integration question internally, with the numbers that appear in a business case.