1
Connect
Use scoped organization credentials and choose which sources may enter the workspace.
Integrations
What OmniManas owns, and what it connects to.
OmniManas is the system of record for its five native surfaces: people, delivery, revenue, customers and knowledge. Everything else stays where it is. Mail, chat, documents, source control, CI, cloud, observability and finance connect in, keep their provenance, and receive approved actions back.
Every signal keeps its source.
A connected record never loses the system it came from. Connectors route through the same tenant, identity and permission boundaries as the rest of the product, and the owning system stays authoritative for anything OmniManas does not natively run.
Meetings & communication
Conversations, calls, decisions and follow-ups
Microsoft TeamsSlackZoomGoogle MeetWebexWhatsApp
Email & productivity
Messages, calendars, contacts and daily work
Microsoft 365Google WorkspaceOutlookGmailGoogle Calendar
Knowledge & files
Documentation, policies, decisions and source material
SharePointNotionConfluenceGoogle DriveDropboxBox
Planning & delivery
Requirements, projects, tasks and commitments
JiraLinearAsanamonday.comClickUpTrello
Code & CI/CD
Repositories, pull requests, checks and releases
GitHubGitLabBitbucketAzure DevOpsGitHub ActionsGitLab CICircleCIJenkinsBuildkiteArgo CD
Observability & incidents
Logs, traces, metrics, errors and response
DatadogSentryGrafanaNew RelicSplunkElasticAmazon CloudWatchPagerDutyOpsgenie
Revenue intelligence
Accounts, pipeline, outreach and conversations
SalesforceHubSpotDynamics 365ApolloOutreachSalesloftGongZoomInfo
Support & service
Customer issues, service workflows and resolution
ZendeskIntercomServiceNowFreshdesk
People operations
HR records, hiring, onboarding and workforce processes
WorkdayBambooHRHiBobRipplingDeelGreenhouseLever
Finance & business data
Revenue, billing, operations and analytical truth
StripeNetSuiteSAPQuickBooksXeroSnowflakeBigQueryRedshiftPostgreSQL
Cloud & runtime
Infrastructure, deployment state and service ownership
AWSMicrosoft AzureGoogle CloudKubernetes
AI & agent ecosystem
Models, governed tools and agent interoperability
OpenAIAnthropicGoogle GeminiAmazon BedrockAzure OpenAIMCP
Connector availability and read/write capabilities follow organization configuration, provider APIs and the permissions granted to each OmniManas workspace.
Each connector maps records, applies policy, returns actions.
2
Resolve
Map external users, accounts, work and conversations to canonical company entities.
3
Govern
Apply role boundaries, source policy, retention and approval requirements.
4
Activate
Read, write or execute through only the capabilities and autonomy level granted to that workflow.
Not limited to a fixed connector catalog.
Connect internal services, data warehouses, feature-flag platforms, billing systems and domain-specific tools without flattening their meaning.
API and events
Bring domain events into the spine and receive approved actions back in the systems that own execution.
MCP interoperability
Expose governed company capabilities to compatible agents without creating a privileged automation path.