Integrations
Module: None (core platform) | Role: Admin (workspace integrations), Any member (personal integrations) | Licence: Free+
Integrations connect external services so agents can access them as tools. There are two scopes:
- Workspace integrations — connected by an admin, shared by all agents in the workspace
- Personal integrations — connected by individual users in their profile, private to them
Workspace Integrations
Connected via Settings → Integrations by a workspace admin or owner.
| Service | What agents get | Credential type |
|---|---|---|
| Slack | Send notifications to channels and DMs | Bot token (auto-connected) |
| Snowflake | Query your Snowflake data via a Cortex Agents MCP server | Programmatic access token |
Once connected, workspace agents declare which integrations they need via mcp_connections:
create_agent(
name="Weekly Platform Update",
mcp_connections=["snowflake"],
triggers=[{type: "cron", schedule: "0 9 * * 1", delivery: ["slack_dm"]}]
)
The integration is resolved at dispatch time — agents reference the type name, never the credential directly.
Personal Integrations
Connected via Profile → Integrations by individual users. Personal integrations are private — not visible to workspace admins or other members.
| Service | What it enables | How to connect |
|---|---|---|
| ev.energy | Linked when you sign in via the ev.energy SSO option — gives Eve read access to your fleet account, charge sessions, and driver analytics | Sign in with ev.energy on the login page; auto-linked, no separate setup |
| Holistics | Query the datasets your Holistics account can see; powers the "Known charging sites" map layer | API key |
Personal integrations take priority over workspace integrations of the same type: Eve uses your own credential rather than any workspace-level one.
Login-time health check
Each time you sign in, the platform validates every personal integration in the background and updates its connection status. If something has expired or been revoked you'll land on a brief confirmation page (/auth/connected) with a Reconnect button next to the affected integration. When all integrations are healthy the page is skipped and you continue straight to the app.
ev.energy
Connecting ev.energy means signing in with the ev.energy option on the login page. Once you've done that, Eve sees your link to the ev.energy fleet platform and can answer questions about your fleet, charging sessions, and driver analytics. There's no separate "Connect" button — the link is the act of signing in. To unlink, sign out and pick a different provider on your next sign-in.
Holistics
Connect Holistics to give Eve and the map access to the datasets your Holistics account can query. This is per-user only — there is no shared workspace Holistics credential because every Holistics user has their own row-level filters, and a shared key would expose data the connecting user is entitled to to every other workspace member.
What it powers:
- Map layer "Known charging sites" — dots on the grid map showing every location where one or more drivers in your Holistics scope has at least one recorded charging session. Visible at city zoom and above.
- Eve queries against Holistics datasets — Eve can run queries against the datasets your Holistics account can see.
Dataset discovery is automatic. The first time you connect, the platform walks the Holistics catalog to find the home, charging, and EVSE datasets by name and field-name patterns. The result is cached for 24 hours, then re-discovered. If your dataset names or field names change, the next discovery picks up the new shape.
If automatic discovery picks the wrong dataset, you can pin the correct one (Profile → Integrations → Holistics → Pin dataset).
How Agents Use Integrations
Agents with mcp_connections automatically receive the right credentials at run time:
- If the requesting user has a personal integration of that type → use it
- Otherwise, if the workspace has a shared integration → use it
- If neither → the connection is omitted; the agent runs without it
This means a workspace-level credential can act as a fallback while individual users override it with their own.
Managing Connections
| Action | Where |
|---|---|
| Connect/disconnect workspace integration | Settings → Integrations |
| Test a workspace integration | Settings → Integrations → Test |
| Connect personal Holistics | Profile → Integrations → Connect |
| Revoke personal integration | Profile → Integrations → Disconnect |