Integrations Hub

Your AI Employees work inside the systems your teams already use. Ema supports 161 integrations natively today, across HR, IT, finance, sales, marketing, communication, productivity, data, and industry systems for healthcare and insurance, with 100+ more coming soon. When you need a system that is not in the catalog, you add it yourself in minutes.

This page gives you the big picture: the two integration types, how connections work, and the full catalog. Workspace admins and builders use it to choose an integration and connect it. For step-by-step setup, go to REST API Integrations or MCP Servers.

The Ema integration catalog: 161 integrations live today across nine business domains, 143 REST API and 18 MCP, with 100+ more coming soon
The catalog at a glance. See the full catalog below.

What you get

  • A growing catalog. 161 integrations in 46 categories, from Workday and SAP SuccessFactors to ServiceNow, Salesforce, Slack, Snowflake, and Epic, with 100+ more coming soon.
  • Two integration types. REST API integrations and MCP servers. Use the ones Ema provides, or add your own of either type.
  • Shared and User connections. One login for the whole Workspace, or each person signs in as themselves.
  • mTLS. Present a client certificate on every outbound request when your system requires mutual TLS.
  • Governance. Ema redacts PII in the LLM calls around every Tool call, and records every Tool call in the audit log.

How integrations reach your AI Employees

Every integration follows the same three steps. You pick an integration, you add a connection with the credentials Ema uses, and your AI Employees call its Tools while they work.

Pick a REST API or MCP integration, add a Shared or User connection, then the AI Employee uses its Tools
From integration to AI Employee in three steps

A Tool is one action an AI Employee can take in an external system, such as "create a ServiceNow incident" or "look up a Workday worker." Each integration holds a set of Tools.

REST API and MCP integrations

Ema supports two integration types. Both appear on the Integrations page, and both use the same Shared and User connections.

REST API integrationsMCP servers
What it isEma calls the system's web API directly. Each Tool is one defined request.Ema connects to a Model Context Protocol (MCP) server. The server lists its own tools.
Where you find itAPI tabMCP Servers tab
Use ours143 REST API integrations in the catalog18 MCP servers in the catalog
Create your ownNew integration → API, then build Tools for any APIAdd server, then point Ema at any MCP server URL
Who can use itAutopilot, and every workflow agent through its Add tool picker, including Custom AgentAutopilot and Orchestrator AI Employees. Not available in Custom Agent.
Learn moreREST API IntegrationsMCP Servers

Pick REST API when you need exact control over each request, or when every AI Employee type must use the Tool. Pick MCP when a vendor already offers an MCP server and you want its full tool set with no Tool building.

The Integrations page

Select Integrations in the left sidebar. The page has these tabs:

TabWhat you do there
AllBrowse the REST API integration catalog. Connect one of ours, or select New integration to create your own.
MCP ServersBrowse the MCP server catalog. Connect one of ours, or select Add server to add your own.
Data SourcesSet up connectors that sync documents into Knowledge bases. See Data Connectors.
ChannelsConfigure where an AI Employee is reachable: Microsoft Teams, Slack, and the embeddable chat SDK. See Embeddable Chat SDK and Microsoft Teams.
TicketingManage the Workspace-level connections a group's ticket queue can run on. See Ticketing.
Audit LogsReview every connection and configuration change, plus each Tool execution, with the actor and timestamp. Filter by role and by action.

On the All and MCP Servers tabs, integrations your Workspace built appear first, under Made in your workspace. The rest of the catalog is grouped by category. Use the search box, the category filters, and the Status filter to find an integration. Each tile shows its connection count and, for REST API integrations, its Tool count.

Connections and connection templates

An integration defines what Ema can do. A connection defines whose credentials Ema uses to do it. You add connections on the integration's Connections tab.

Each connection you add is a connection template: a named, reusable setup that holds the connection type, the shared settings (such as a base URL or OAuth client ID), the groups that can use it, and the Tools it allows. One integration can have several connection templates. For example, you can add one named "Production" and one named "Sandbox," or one per region.

Shared or User

Every connection template has a type. You choose it when you add the connection. The type decides whose account the Tools act as: one account for everyone, or each person's own. It does not decide whether you need your own client ID and client secret. That depends on how the integration authenticates. See When you need your own client ID and secret.

Shared connection: everyone uses one login. User connection: each person uses their own login.
Shared connections act as one account. User connections act as the person who asked.
Shared connectionUser connection
In the UI"One login everyone in your workspace uses.""Each user signs in with their own credentials."
Who signs inAn admin, onceEach person, with Connect my account
What the admin entersThe integration's settings and the account credentials: the API key, the username and password, or the OAuth sign-inThe integration's settings only, such as the base URL and, when needed, the client ID and client secret
What each person entersNothingTheir own account credentials: they sign in, or paste their own API key or password
Whose access the Tools useThe one shared accountThe account of the person the AI Employee works for
Use it whenEvery request must come from one account, such as [email protected]Each person must see only their own data, such as their own inbox or calendar

Example: Gmail. A support AI Employee must send every reply from [email protected]. Add a Shared connection and sign in once as that mailbox. An assistant AI Employee must read each person's own inbox. Add a User connection. Each person connects their own Gmail, and the AI Employee only reaches the mailbox of the person it works for.

When you need your own client ID and secret

A client ID and client secret identify an OAuth app you register with the provider. They do not identify a person. They belong to the connection template, so an admin enters them once, for a Shared or a User connection. People who connect a User connection never see or enter them. They only sign in.

AuthenticationDo you bring your own client ID and secret?
OAuth sign-in (OAuth 2.0, or OAuth 2.1 on an MCP server)Only when the connection form shows Client ID and Client secret fields. A REST API integration you build always does: register an OAuth app with the provider first. Where the form shows no such fields, Ema provides the sign-in app and you only sign in.
OAuth 2.0 Client Credentials and OAuth 2.0 (Refresh Token)Yes, always. Ema uses them to get access tokens without a person signing in.
API key or Basic authNo. There is no OAuth app. The API key, or the username and password, is the account credential itself.

For MCP servers, the form tells you which case applies. When the server registers Ema automatically, you leave Client ID and Client secret blank. When it does not, the form asks for a pre-registered Client ID. See MCP Servers.

Add a connection

Who can edit. Workspace admins can always edit an integration and its connections. To let someone else edit one integration, add them under Integration admins on that integration's Permissions tab.

  1. On the All or MCP Servers tab, open the integration.
  2. On the Connections tab, select Add, then select Shared connection or User connection.
  3. In Connection name, enter a name that tells connections apart, such as "Production" or "EU Region."
  4. In Assign to groups, keep Not assigned (available everywhere), or pick the groups that can use this connection.
  5. Fill in the Authentication fields. For a Shared connection, you enter everything, including the account credentials. For a User connection, you enter only the integration's settings, such as the base URL and any client ID and client secret. Each person adds their own account credentials when they connect.
  6. Under Enabled tools, clear any Tool this connection must not run.
  7. Select Save & connect to sign in now, or Save without connecting to finish later.

For OAuth integrations, the form shows a redirect URI. Copy it into your OAuth provider's app settings before you connect.

Manage connections

Each connection template on the Connections tab shows its type, its status, and how many people have connected. From there you can:

  • Make default. AI Employees that do not pick a connection use the default one.
  • Connect, Reconnect, or Disconnect a Shared connection.
  • Connect my account for a User connection, and see the list of Connected users.
  • Check AI Employees using this connection before you change or delete it. Ema blocks the delete of a connection that AI Employees still use.

Connections restricted to some groups show a Group-restricted badge. Credentials are encrypted at rest and are never shown again after you save them. When an OAuth token expires, Ema refreshes it on the next Tool call.

Retiring apps

Ema is retiring some older versions of apps in favor of versions that Ema builds and maintains. An older version shows a Retiring badge on its tile, on its integration page, and on its Tools in the AI Employee builder. The new version can have the same name, so the badge is how you tell the two apart.

While an app is retiring:

  • Existing connections keep working. You cannot set up new connections for the app.
  • AI Employees keep running. An AI Employee that already uses the app's Tools keeps working, and you can still edit and publish it.
  • Nothing new can start using the app. You cannot add its Tools to an agent, import an AI Employee that adds its Tools, or set up a new poll trigger on it.
  • The tile stays only while you use it. A retiring app appears in the catalog only while someone in your Workspace still has a connection through it.

Switch to the new version

  1. On the Integrations page, open the version of the app without the Retiring badge and add a connection.
  2. Open each AI Employee that uses the retiring app. On each agent, add the matching Tools from the new version, then remove the retiring Tools.
  3. If a poll trigger watches the retiring app, point it at the new version.
  4. Test the AI Employee, then publish it.
  5. When nothing uses the retiring app, disconnect it. After you disconnect, you may not be able to connect it again. When nobody in your Workspace is connected, the app leaves the catalog.

If the catalog has no other version of the app, create your own REST API integration or contact your Ema team.

mTLS

Some systems accept requests only from callers that present a trusted client certificate (mutual TLS). Ema supports mTLS on REST API integration connections, with any authentication type.

  1. When you add or edit a connection, expand Advanced.
  2. Paste your Client certificate (PEM) and Client private key (PEM).
  3. Save the connection.

Ema presents the certificate during the TLS handshake on every request through that connection. The certificate works in addition to the connection's authentication, not in place of it.

PII and audit around Tool calls

  • PII redaction around Tool calls. Ema redacts PII in every LLM call, including the LLM calls that decide on a Tool call and that read its result. The Tool call itself is not redacted, so the external system receives the values it needs to do its job.
  • Audit trail. Ema records every Tool call, whether it runs from an AI Employee, from Autopilot, or from a Test panel. Review calls on the integration's Activity tab (Executions), and configuration changes on the Audit Logs tab.

Full catalog

Ema supports these 161 integrations natively: 143 REST API integrations and 18 MCP servers. The Type column tells you where to find each one and which setup guide applies: REST API integrations are on the API tab (REST API Integrations), and MCP servers are on the MCP Servers tab (MCP Servers). Close, GitHub, Gmail, Google Docs, Google Drive, Google Sheets, Miro, Mixpanel, and Stripe also have MCP servers on the MCP Servers tab. The catalog lists each of them once, as a REST API integration.

100+ more integrations coming soon. Ema is adding more than 100 further integrations across HR, IT, finance, sales and marketing, and productivity. Until the one you need is live, create your own REST API integration or add your own MCP server.

HR (21)

IntegrationCategoryType
AshbyATSREST API
GreenhouseATSREST API
iCIMSATSREST API
LeverATSREST API
SmartRecruitersATSREST API
WorkableATSMCP
BambooHRHRISREST API
HiBobHRISREST API
Oracle Fusion Cloud HCMHRISREST API
RipplingHRISREST API
SAP SuccessFactorsHRISREST API
UKG ProHRISREST API
WorkdayHRISREST API
ADP Workforce NowPayrollREST API
PaylocityPayrollREST API
DeelPayrollMCP
GustoPayrollMCP
Coursera for BusinessSkills & learningREST API
HackerRank for WorkSkills & learningREST API
LinkedIn LearningSkills & learningREST API
Thrive LearningSkills & learningREST API

IT (23)

IntegrationCategoryType
Bitbucket CloudDeveloper toolsREST API
GitHubDeveloper toolsREST API
GitLab CI/CDDeveloper toolsREST API
GitLab Extended APIsDeveloper toolsREST API
GitLab Groups and AdministrationDeveloper toolsREST API
GitLab Projects and CollaborationDeveloper toolsREST API
Zoom AppsDeveloper toolsREST API
GitLabDeveloper toolsMCP
SentryDeveloper toolsMCP
Jamf ProDevice managementREST API
FreshdeskHelpdeskREST API
ZendeskHelpdeskREST API
IntercomHelpdeskMCP
Okta Workforce IdentityIdentity & accessREST API
Zoom SCIM 2Identity & accessREST API
IdentityCheckIdentity verificationREST API
FreshserviceITSMREST API
JiraITSMREST API
ServiceNowITSMREST API
AWS Cost ExplorerObservability & cloudREST API
GrafanaObservability & cloudREST API
Zoom Quality of Service SubscriptionObservability & cloudREST API
VantageObservability & cloudMCP

Finance (28)

IntegrationCategoryType
QuickBooks OnlineAccounting & taxREST API
sevDeskAccounting & taxREST API
XeroAccounting & taxREST API
FixerCurrency exchangeREST API
NetSuiteERPREST API
Oracle Fusion Cloud FinancialsERPREST API
Oracle Fusion Cloud Joint Venture and IntercompanyERPREST API
Oracle Fusion Cloud Payables and ExpensesERPREST API
Oracle Fusion Cloud Project Financials and GrantsERPREST API
Oracle Fusion Cloud Project ManagementERPREST API
Oracle Fusion Cloud Project Planning and ResourcesERPREST API
Oracle Fusion Cloud Receivables, Cash and PaymentsERPREST API
SAP S/4HANA Cloud (Business Partners and Procurement Reads)ERPREST API
BILLPaymentsREST API
Flutterwave v4PaymentsREST API
SquarePaymentsREST API
StripePaymentsREST API
Stripe Specialist ProductsPaymentsREST API
PayPalPaymentsMCP
CoupaProcurementREST API
Oracle Fusion Cloud Catalogs, Spend and Supplier AssessmentsProcurementREST API
Oracle Fusion Cloud Purchasing and RequisitionsProcurementREST API
Oracle Fusion Cloud Suppliers and AgreementsProcurementREST API
SAP AribaProcurementREST API
BILL Spend & ExpenseSpend & expenseREST API
BrexSpend & expenseREST API
RampSpend & expenseREST API
SAP ConcurSpend & expenseREST API

Sales (20)

IntegrationCategoryType
IroncladCommerce & contractsREST API
Zoom CommerceCommerce & contractsREST API
Capsule CRMCRMREST API
CloseCRMREST API
Dynamics 365 SalesCRMREST API
HubSpot Sales UserCRMREST API
KommoCRMREST API
Pipeline CRMCRMREST API
SalesforceCRMREST API
SalesmateCRMREST API
HubSpotCRMMCP
PipedriveCRMMCP
ZoomInfoData enrichmentREST API
ApolloProspectingREST API
LinkedIn Sales Navigator AnalyticsProspectingREST API
GongRevenue intelligenceREST API
Zoom Revenue AcceleratorRevenue intelligenceREST API
PersistIQSales engagementREST API
SalesloftSales engagementREST API
Zoom Auto DialerSales engagementREST API

Marketing (7)

IntegrationCategoryType
Zoom Webinars Plus & EventsEvents & webinarsREST API
MopinionFeedback & surveysREST API
Adobe AnalyticsMarketing analyticsREST API
Google AnalyticsMarketing analyticsREST API
Google Analytics AdminMarketing analyticsREST API
Adobe Marketo EngageMarketing automationREST API
LinkedInSocial mediaREST API

Communication (24)

IntegrationCategoryType
Zoom SchedulerCalendar & schedulingREST API
CalendlyCalendar & schedulingMCP
Google CalendarCalendar & schedulingMCP
AgentMailEmail & messagingREST API
ChatworkEmail & messagingREST API
GmailEmail & messagingREST API
Microsoft TeamsEmail & messagingREST API
OutlookEmail & messagingREST API
Slack ToolsEmail & messagingREST API
TwilioEmail & messagingREST API
WhatsApp BusinessEmail & messagingREST API
Google ChatEmail & messagingMCP
Genesys Cloud CX (Workforce)Phone & contact centerREST API
Zoom Contact CenterPhone & contact centerREST API
Zoom Number ManagementPhone & contact centerREST API
Zoom PhonePhone & contact centerREST API
Zoom Quality ManagementPhone & contact centerREST API
Zoom Virtual AgentPhone & contact centerREST API
Zoom Workforce ManagementPhone & contact centerREST API
Google MeetVideo meetingsREST API
Zoom ClipsVideo meetingsREST API
Zoom RoomsVideo meetingsREST API
Zoom Video ManagementVideo meetingsREST API
ZoomVideo meetingsMCP

Productivity (27)

IntegrationCategoryType
GeminiAI & writingREST API
WriterAI & writingREST API
Zoom AI CompanionAI & writingREST API
CodaDocuments & presentationsREST API
Google DocsDocuments & presentationsREST API
Zoom My NotesDocuments & presentationsREST API
Google SlidesDocuments & presentationsMCP
DocuSealE-signatureREST API
BoxFile storageREST API
DropboxFile storageREST API
Google DriveFile storageREST API
OneDriveFile storageREST API
SharePoint SitesFile storageREST API
FormdeskForms & spreadsheetsREST API
FormsiteForms & spreadsheetsREST API
Google SheetsForms & spreadsheetsREST API
Microsoft ExcelForms & spreadsheetsREST API
ConfluenceKnowledge baseREST API
NotionKnowledge baseREST API
Google TasksProjects & tasksREST API
monday.comProjects & tasksREST API
OneDeskProjects & tasksREST API
StreamtimeProjects & tasksREST API
ClickUpProjects & tasksMCP
LinearProjects & tasksMCP
TrelloProjects & tasksMCP
MiroWhiteboardsREST API

Data (5)

IntegrationCategoryType
DatabricksAnalytics & BIREST API
MixpanelAnalytics & BIREST API
TableauAnalytics & BIREST API
Twilio SegmentCustomer dataREST API
SnowflakeData warehouseREST API

Industry (6)

IntegrationCategoryType
athenaOneHealthcare EHRREST API
EpicHealthcare EHRREST API
Guidewire BillingCenterInsuranceREST API
Guidewire ClaimCenterInsuranceREST API
Guidewire PolicyCenterInsuranceREST API
Zoom HealthcareTelehealthREST API

What's next

  • REST API Integrations: connect a REST API integration from the catalog, or create your own.
  • MCP Servers: connect an MCP server and use it from Autopilot and Orchestrator AI Employees.
  • Data Connectors: sync documents from external systems into Knowledge bases.

Last updated: Nov 3, 2026