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.
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.
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 integrations | MCP servers | |
|---|---|---|
| What it is | Ema 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 it | API tab | MCP Servers tab |
| Use ours | 143 REST API integrations in the catalog | 18 MCP servers in the catalog |
| Create your own | New integration → API, then build Tools for any API | Add server, then point Ema at any MCP server URL |
| Who can use it | Autopilot, and every workflow agent through its Add tool picker, including Custom Agent | Autopilot and Orchestrator AI Employees. Not available in Custom Agent. |
| Learn more | REST API Integrations | MCP 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:
| Tab | What you do there |
|---|---|
| All | Browse the REST API integration catalog. Connect one of ours, or select New integration to create your own. |
| MCP Servers | Browse the MCP server catalog. Connect one of ours, or select Add server to add your own. |
| Data Sources | Set up connectors that sync documents into Knowledge bases. See Data Connectors. |
| Channels | Configure where an AI Employee is reachable: Microsoft Teams, Slack, and the embeddable chat SDK. See Embeddable Chat SDK and Microsoft Teams. |
| Ticketing | Manage the Workspace-level connections a group's ticket queue can run on. See Ticketing. |
| Audit Logs | Review 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 | User connection | |
|---|---|---|
| In the UI | "One login everyone in your workspace uses." | "Each user signs in with their own credentials." |
| Who signs in | An admin, once | Each person, with Connect my account |
| What the admin enters | The integration's settings and the account credentials: the API key, the username and password, or the OAuth sign-in | The integration's settings only, such as the base URL and, when needed, the client ID and client secret |
| What each person enters | Nothing | Their own account credentials: they sign in, or paste their own API key or password |
| Whose access the Tools use | The one shared account | The account of the person the AI Employee works for |
| Use it when | Every 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.
| Authentication | Do 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 auth | No. 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.
- On the All or MCP Servers tab, open the integration.
- On the Connections tab, select Add, then select Shared connection or User connection.
- In Connection name, enter a name that tells connections apart, such as "Production" or "EU Region."
- In Assign to groups, keep Not assigned (available everywhere), or pick the groups that can use this connection.
- 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.
- Under Enabled tools, clear any Tool this connection must not run.
- 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
- On the Integrations page, open the version of the app without the Retiring badge and add a connection.
- 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.
- If a poll trigger watches the retiring app, point it at the new version.
- Test the AI Employee, then publish it.
- 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.
- When you add or edit a connection, expand Advanced.
- Paste your Client certificate (PEM) and Client private key (PEM).
- 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)
| Integration | Category | Type |
|---|---|---|
| Ashby | ATS | REST API |
| Greenhouse | ATS | REST API |
| iCIMS | ATS | REST API |
| Lever | ATS | REST API |
| SmartRecruiters | ATS | REST API |
| Workable | ATS | MCP |
| BambooHR | HRIS | REST API |
| HiBob | HRIS | REST API |
| Oracle Fusion Cloud HCM | HRIS | REST API |
| Rippling | HRIS | REST API |
| SAP SuccessFactors | HRIS | REST API |
| UKG Pro | HRIS | REST API |
| Workday | HRIS | REST API |
| ADP Workforce Now | Payroll | REST API |
| Paylocity | Payroll | REST API |
| Deel | Payroll | MCP |
| Gusto | Payroll | MCP |
| Coursera for Business | Skills & learning | REST API |
| HackerRank for Work | Skills & learning | REST API |
| LinkedIn Learning | Skills & learning | REST API |
| Thrive Learning | Skills & learning | REST API |
IT (23)
| Integration | Category | Type |
|---|---|---|
| Bitbucket Cloud | Developer tools | REST API |
| GitHub | Developer tools | REST API |
| GitLab CI/CD | Developer tools | REST API |
| GitLab Extended APIs | Developer tools | REST API |
| GitLab Groups and Administration | Developer tools | REST API |
| GitLab Projects and Collaboration | Developer tools | REST API |
| Zoom Apps | Developer tools | REST API |
| GitLab | Developer tools | MCP |
| Sentry | Developer tools | MCP |
| Jamf Pro | Device management | REST API |
| Freshdesk | Helpdesk | REST API |
| Zendesk | Helpdesk | REST API |
| Intercom | Helpdesk | MCP |
| Okta Workforce Identity | Identity & access | REST API |
| Zoom SCIM 2 | Identity & access | REST API |
| IdentityCheck | Identity verification | REST API |
| Freshservice | ITSM | REST API |
| Jira | ITSM | REST API |
| ServiceNow | ITSM | REST API |
| AWS Cost Explorer | Observability & cloud | REST API |
| Grafana | Observability & cloud | REST API |
| Zoom Quality of Service Subscription | Observability & cloud | REST API |
| Vantage | Observability & cloud | MCP |
Finance (28)
| Integration | Category | Type |
|---|---|---|
| QuickBooks Online | Accounting & tax | REST API |
| sevDesk | Accounting & tax | REST API |
| Xero | Accounting & tax | REST API |
| Fixer | Currency exchange | REST API |
| NetSuite | ERP | REST API |
| Oracle Fusion Cloud Financials | ERP | REST API |
| Oracle Fusion Cloud Joint Venture and Intercompany | ERP | REST API |
| Oracle Fusion Cloud Payables and Expenses | ERP | REST API |
| Oracle Fusion Cloud Project Financials and Grants | ERP | REST API |
| Oracle Fusion Cloud Project Management | ERP | REST API |
| Oracle Fusion Cloud Project Planning and Resources | ERP | REST API |
| Oracle Fusion Cloud Receivables, Cash and Payments | ERP | REST API |
| SAP S/4HANA Cloud (Business Partners and Procurement Reads) | ERP | REST API |
| BILL | Payments | REST API |
| Flutterwave v4 | Payments | REST API |
| Square | Payments | REST API |
| Stripe | Payments | REST API |
| Stripe Specialist Products | Payments | REST API |
| PayPal | Payments | MCP |
| Coupa | Procurement | REST API |
| Oracle Fusion Cloud Catalogs, Spend and Supplier Assessments | Procurement | REST API |
| Oracle Fusion Cloud Purchasing and Requisitions | Procurement | REST API |
| Oracle Fusion Cloud Suppliers and Agreements | Procurement | REST API |
| SAP Ariba | Procurement | REST API |
| BILL Spend & Expense | Spend & expense | REST API |
| Brex | Spend & expense | REST API |
| Ramp | Spend & expense | REST API |
| SAP Concur | Spend & expense | REST API |
Sales (20)
| Integration | Category | Type |
|---|---|---|
| Ironclad | Commerce & contracts | REST API |
| Zoom Commerce | Commerce & contracts | REST API |
| Capsule CRM | CRM | REST API |
| Close | CRM | REST API |
| Dynamics 365 Sales | CRM | REST API |
| HubSpot Sales User | CRM | REST API |
| Kommo | CRM | REST API |
| Pipeline CRM | CRM | REST API |
| Salesforce | CRM | REST API |
| Salesmate | CRM | REST API |
| HubSpot | CRM | MCP |
| Pipedrive | CRM | MCP |
| ZoomInfo | Data enrichment | REST API |
| Apollo | Prospecting | REST API |
| LinkedIn Sales Navigator Analytics | Prospecting | REST API |
| Gong | Revenue intelligence | REST API |
| Zoom Revenue Accelerator | Revenue intelligence | REST API |
| PersistIQ | Sales engagement | REST API |
| Salesloft | Sales engagement | REST API |
| Zoom Auto Dialer | Sales engagement | REST API |
Marketing (7)
| Integration | Category | Type |
|---|---|---|
| Zoom Webinars Plus & Events | Events & webinars | REST API |
| Mopinion | Feedback & surveys | REST API |
| Adobe Analytics | Marketing analytics | REST API |
| Google Analytics | Marketing analytics | REST API |
| Google Analytics Admin | Marketing analytics | REST API |
| Adobe Marketo Engage | Marketing automation | REST API |
| Social media | REST API |
Communication (24)
| Integration | Category | Type |
|---|---|---|
| Zoom Scheduler | Calendar & scheduling | REST API |
| Calendly | Calendar & scheduling | MCP |
| Google Calendar | Calendar & scheduling | MCP |
| AgentMail | Email & messaging | REST API |
| Chatwork | Email & messaging | REST API |
| Gmail | Email & messaging | REST API |
| Microsoft Teams | Email & messaging | REST API |
| Outlook | Email & messaging | REST API |
| Slack Tools | Email & messaging | REST API |
| Twilio | Email & messaging | REST API |
| WhatsApp Business | Email & messaging | REST API |
| Google Chat | Email & messaging | MCP |
| Genesys Cloud CX (Workforce) | Phone & contact center | REST API |
| Zoom Contact Center | Phone & contact center | REST API |
| Zoom Number Management | Phone & contact center | REST API |
| Zoom Phone | Phone & contact center | REST API |
| Zoom Quality Management | Phone & contact center | REST API |
| Zoom Virtual Agent | Phone & contact center | REST API |
| Zoom Workforce Management | Phone & contact center | REST API |
| Google Meet | Video meetings | REST API |
| Zoom Clips | Video meetings | REST API |
| Zoom Rooms | Video meetings | REST API |
| Zoom Video Management | Video meetings | REST API |
| Zoom | Video meetings | MCP |
Productivity (27)
| Integration | Category | Type |
|---|---|---|
| Gemini | AI & writing | REST API |
| Writer | AI & writing | REST API |
| Zoom AI Companion | AI & writing | REST API |
| Coda | Documents & presentations | REST API |
| Google Docs | Documents & presentations | REST API |
| Zoom My Notes | Documents & presentations | REST API |
| Google Slides | Documents & presentations | MCP |
| DocuSeal | E-signature | REST API |
| Box | File storage | REST API |
| Dropbox | File storage | REST API |
| Google Drive | File storage | REST API |
| OneDrive | File storage | REST API |
| SharePoint Sites | File storage | REST API |
| Formdesk | Forms & spreadsheets | REST API |
| Formsite | Forms & spreadsheets | REST API |
| Google Sheets | Forms & spreadsheets | REST API |
| Microsoft Excel | Forms & spreadsheets | REST API |
| Confluence | Knowledge base | REST API |
| Notion | Knowledge base | REST API |
| Google Tasks | Projects & tasks | REST API |
| monday.com | Projects & tasks | REST API |
| OneDesk | Projects & tasks | REST API |
| Streamtime | Projects & tasks | REST API |
| ClickUp | Projects & tasks | MCP |
| Linear | Projects & tasks | MCP |
| Trello | Projects & tasks | MCP |
| Miro | Whiteboards | REST API |
Data (5)
| Integration | Category | Type |
|---|---|---|
| Databricks | Analytics & BI | REST API |
| Mixpanel | Analytics & BI | REST API |
| Tableau | Analytics & BI | REST API |
| Twilio Segment | Customer data | REST API |
| Snowflake | Data warehouse | REST API |
Industry (6)
| Integration | Category | Type |
|---|---|---|
| athenaOne | Healthcare EHR | REST API |
| Epic | Healthcare EHR | REST API |
| Guidewire BillingCenter | Insurance | REST API |
| Guidewire ClaimCenter | Insurance | REST API |
| Guidewire PolicyCenter | Insurance | REST API |
| Zoom Healthcare | Telehealth | REST 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.