REST API Integrations
A REST API integration lets an AI Employee act in a system through that system's web API. Each Tool in the integration is one defined request, such as "create an incident" or "get a worker." Ema provides 27 REST API integrations ready to connect, with more coming soon, listed in the Integrations Hub catalog. For any other API, you create your own.
This page is for builders and Workspace admins. It covers how to connect an integration, how to create your own, and how to give its Tools to an AI Employee.
Ema adds the connection's credentials to each request, so your Tools never handle secrets. If the connection has an mTLS certificate, Ema presents it too.
Use an integration from the catalog
- Select Integrations in the left sidebar. The All tab opens.
- Find the integration. Use the search box, or select a category filter such as CRM or Ticketing.
- Open the integration and go to its Connections tab.
- Add a Shared or User connection. See Add a connection.
- Give its Tools to an AI Employee.
Ema builds the Tools in catalog integrations. You connect them and use them, with nothing to build.
The integration page
Every REST API integration, whether Ema built it or you did, has the same four tabs.
| Tab | What it shows |
|---|---|
| Connections | The connection templates for this integration, their status, and who has connected. Add, connect, or delete connections here. |
| Configure | How Ema signs in to the integration (the authentication scheme and its fields), and the list of Tools your AI Employees can use, with each Tool's status. |
| Permissions | Integration admins: the people who can edit this integration and its Tools. Workspace admins always have access. |
| Activity | Executions: each Tool run, filterable by Tool, caller, and date range. Admin activity: changes to the integration. |
Create your own
When the system you need is not in the catalog, wrap its API in your own integration. On the All tab, select New integration → API. Then set the authentication, add a connection, and build the Tools. Custom Integrations walks through each step, and The Tool Editor covers Tool building.
Ema supports OAuth 2.0 (including Client Credentials and Refresh Token), API key, Basic auth, and no auth. To bring in an integration built in another Workspace or environment, select New integration → Import integration.
Give Tools to an AI Employee
You attach Tools to an agent in an AI Employee's workflow.
- Open the AI Employee in the AI Employee builder and select the agent.
- In the agent's panel, select Add tool.
- Pick the Integration, the Tool, and the Connection it uses.
- Optional: enter an Alias, such as
crm_lookup. The agent refers to the Tool by this name. An alias starts with a letter or underscore and contains only letters, numbers, and underscores. - Select Add.
The picker lists only connections that allow the Tool. If no connection allows it, add one or turn the Tool on under Enabled tools in the connection. Autopilot can also run REST API Tools while it works with you.
You can publish the AI Employee before anyone has connected, but the connection must be live at run time:
- Shared connection with no login: the run fails, and the person is told to ask an admin to finish the connection.
- User connection: the person is prompted to connect their own account during the run.
What's next
- Custom Integrations: build your own REST API integration end to end.
- The Tool Editor: define a Tool's inputs, request, and outputs.
- MCP Servers: connect MCP servers for Autopilot and Orchestrator AI Employees.