Knowledge
Google Drive
Bring current documents and working references into a responsibility.
Harmony / Connections & deployment
Your systems.
Connected to the work.
Find the connections your workflow needs, choose your infrastructure and model providers, and plan the rollout with the people who run your systems. Start with familiar tools or scope a custom integration.
An expanding, administrator-managed catalog
Start with the tools your team knows.
Documents supply context. Business systems show what changed. Communication channels bring the right update or decision to the right person.
Common connection targets are shown below. Availability and supported operations are confirmed for your deployment.
14 connection targets shown
Knowledge
SharePoint & OneDrive
Use the policies, project records and team material your people already maintain.
Knowledge
Notion & Confluence
Connect company guidance, operating briefs and product knowledge.
Mail & calendar
Gmail
Follow permitted correspondence and prepare the next useful reply or handoff.
Mail & calendar
Outlook & Microsoft 365
Connect relevant email, meetings and calendar commitments to ongoing work.
Communication
Slack
Deliver relevant updates and let authorized people review permitted low-risk actions.
Communication
Microsoft Teams
Put a scoped handoff or decision request into the team’s existing communication flow.
Communication
WhatsApp Business
Reach an authorized person with a concise update or a permitted low-risk approval request.
Business systems
Salesforce & HubSpot
Connect accounts, customer commitments and commercial opportunities.
Business systems
Zendesk & ServiceNow
Investigate service issues, recurring friction and unresolved handoffs.
Business systems
SAP, Dynamics 365 & NetSuite
Connect order, delivery, procurement and finance prerequisites.
Product & data
Jira & Linear
Relate a product goal, customer pattern or delivery dependency to existing work.
Product & data
GitHub & GitLab
Investigate product changes and prepare reviewable engineering work.
Product & data
Snowflake & SQL data
Ground KPI interpretation, business intelligence and investigations in permitted data.
Notifications and low-risk approvals
Keep the decision close.
Keep the authority explicit.
In the channel model, an update reaches the approved Slack, Teams, email or WhatsApp Business account. The company administrator decides which defined low-risk actions may be approved there, and by whom.
A decision in the flow of workExample handoff
Company administrator
Decide what the channel may do.
Notifications and approvals are separate permissions. The admin chooses the action classes, recipients and authorized approvers.
Notification destinationAlex’s approved business account
Send the useful part.
Limit the notification to the approved summary and recipient. Keep restricted supporting records behind their existing access controls.
Authorize a specific action.
The channel, person, action and relevant limits must match company policy. A general permission to receive updates is not a permission to approve.
Keep the work and decision together.
The approval refers to a defined proposal and is retained with the work. Higher-impact or out-of-scope decisions use the appropriate review in Harmony.
Beyond the common catalog
Your company’s systems
belong in the picture too.
A useful responsibility may depend on an internal application, a restricted database or a company-specific process. Scope those connections with the same care as a familiar SaaS tool.
Private company connectors
Keep an internal integration in the organization’s own authorized catalog. Define which identities, agents and environments may use it.
Custom enterprise connections
Connect the fields and operations needed from an ERP, industry system or legacy application. Agree the interface and integration work with its owner.
Open and extensible interfaces
Use suitable APIs and MCP-based tools where they fit. A standard interface helps expose a capability; the company still approves its actual access and authority.
Missing a system? Bring it to the first scope discussion. Define the job, the required information and the operations before deciding how the connection should be delivered.
Discuss a custom connectionWork across company boundaries
Let partners work with your agents.
Choose what can travel in each direction.
Give a customer or partner access to a selected company agent, or let your agents use approved third-party agents and services. Your administrator defines each relationship: who can participate, which knowledge and tools it can use, and which actions are permitted.
PartnerYour agent
Offer a capability with a clear boundary.
A customer asks your delivery agent about its own orders. The agent uses the customer’s approved status records and returns the agreed fields.
- Who may use it
- Named customer users or agents authorized for this relationship.
- Knowledge it can use
- A customer-scoped order-status data space, bound to the delivery agent.
- Tools it may call
- Your order-system connector, limited to approved status lookups.
- What it may do
- Answer status questions for that customer. Pricing, other customers’ records and order changes stay outside the scope.
Your agentPartner service
Use a partner’s capability on your terms.
Your procurement agent asks an approved supplier agent for dispatch status. The supplier’s access rules and your company’s outbound policy apply together. Only the permitted order reference is sent; the response returns to the same work.
- Who may call it
- The internal agents and people your company has authorized.
- Knowledge it may share
- Only the allowed fields from the bound supplier-work data space.
- Which connection it uses
- The approved supplier connector and remote agent or service endpoint.
- What it may request
- Read the agreed dispatch status. Internal documents, unapproved recipients and purchase commitments remain outside the request.
Two directions. Separate permissions. Bind each relationship to its agents, data spaces, connectors and permitted operations. Set its owner, review point and pause conditions; reassess current access before continuing work. Permission to share information and permission to process it with a model remain distinct.
Explore cross-company workVendor-agnostic by design
Choose the providers.
Keep the operating model.
Choose hosting, model processing and business systems separately. Shape the deployment around your organization’s requirements and approved interfaces, while keeping the responsibility and its policies explicit.
Your cloud or IaaS
Use compute, storage and networking from your chosen infrastructure-as-a-service (IaaS) provider, or scope a private-cloud or on-premises environment. Agree the infrastructure and operating responsibilities for the deployment.
Your approved models
Choose suitable self-hosted models or approved model-provider deployments for the work. Evaluate compatibility, data terms and cost; each source’s processing restrictions still determine which choices are eligible.
Your systems and partners
Connect through approved connectors, suitable APIs and open interfaces such as MCP. Partners can keep their own agent platforms; agree the capabilities, information and permissions exchanged at the boundary.
Deployment compatibility and supported operations are confirmed for the selected infrastructure, models and connections.
From connection to rollout
Make the first workflow operable.
A working connector is only the start. Agree who runs the deployment, test the end-to-end job and define what a successful first rollout should demonstrate.
Name the operating owners
Identify the people responsible for infrastructure, connector credentials, upgrades and support. Agree who responds when a dependency changes or a connection fails.
Rehearse the complete job
Use representative records to check field mappings, API limits and required operations. Test unavailable systems, duplicate updates and reconnection before relying on the workflow.
Set the rollout criteria
Start with one responsibility and a small group. Agree the expected result, review period and conditions for pausing or expanding the scope.
One workflow is enough to start
What would you
stop chasing?
Bring one recurring process. We’ll map what an agent can carry forward,
the decisions your team keeps and how to evaluate the result.