Connector and action framework

Connect enterprise systems without flattening their authority.

Preserve source identity, permissions, lineage, freshness, and action boundaries while exposing one governed interface to search, assistants, and agents.

Identity
Source policy
Normalized context
Agent tool
Action evidence

Illustrative connector control path

Connector catalog

Start from the systems already inside the workflow.

Catalog entries describe integration patterns to evaluate. They are not a claim of general availability, certification, or write access. Authentication, API coverage, rate limits, regional support, and action scope are confirmed per engagement.

28 patterns shown

Slack

Collaboration

Knowledge · eventsIntegration pattern

Microsoft Teams

Collaboration

Knowledge · eventsIntegration pattern

Google Drive

Knowledge

Files · ACLsIntegration pattern

SharePoint

Knowledge

Files · ACLsIntegration pattern

Confluence

Knowledge

Pages · ACLsIntegration pattern

Notion

Knowledge

Pages · ACLsIntegration pattern

Salesforce

Revenue

Records · scoped actionsIntegration pattern

HubSpot

Revenue

Records · scoped actionsIntegration pattern

Gong

Revenue

Calls · metadataIntegration pattern

Zendesk

Service

Cases · scoped actionsIntegration pattern

ServiceNow

Service

Records · scoped actionsIntegration pattern

Jira

Engineering

Issues · scoped actionsIntegration pattern

GitHub

Engineering

Code · issues · eventsIntegration pattern

GitLab

Engineering

Code · issues · eventsIntegration pattern

Datadog

Engineering

Telemetry · eventsIntegration pattern

PagerDuty

Engineering

Incidents · scoped actionsIntegration pattern

Snowflake

Data

Tables · governed queriesIntegration pattern

Databricks

Data

Tables · governed queriesIntegration pattern

BigQuery

Data

Tables · governed queriesIntegration pattern

Workday

People

Records · sensitive scopesIntegration pattern

SAP

Operations

Records · process eventsIntegration pattern

Oracle

Operations

Records · process eventsIntegration pattern

Coupa

Procurement

Suppliers · approvalsIntegration pattern

Okta

Identity

Users · groups · eventsIntegration pattern

Microsoft Entra ID

Identity

Users · groups · eventsIntegration pattern

Box

Knowledge

Files · ACLsIntegration pattern

OneDrive

Knowledge

Files · ACLsIntegration pattern

S3

Data

Objects · policy scopesIntegration pattern

Connector control model

A connector is a security boundary, not just a data pipe.

Authenticate

Use approved delegated or service identity and keep credentials outside model context.

Authorize

Resolve source, object, record, field, and action policy at the point of use.

Normalize

Preserve source authority, ownership, sensitivity, lineage, and freshness metadata.

Operate

Observe sync health, quotas, failures, coverage, latency, and owner escalation.

Act

Validate parameters, idempotency, approvals, destinations, and compensating actions.

Evidence

Record principal, request, source scope, policy outcome, tool result, and business state change.

Architecture session

Bring one consequential workflow. Leave with a governed agent blueprint.

We will map the context, systems, decisions, controls, actions, and success measures together.

Talk to an architect