Integrations / Sana from Workday
Sana from Workday
Sana Enterprise (Workday) AI workspace that hosts Telara as a remote MCP server so authorized workspace users can invoke governed Telara tools. Host-only; Telara holds no Sana credential.
See connection fields
What Telara does
Capability matrix
Before you connect
Prerequisites
A Sana Enterprise workspace. Custom MCP integrations are not available on other Sana plans.
A Sana workspace admin who can add integrations and choose which users or groups see them.
Vendor setup
Get the credential
1
Add Telara as a custom MCP integration in Sana
In Sana open Workspace settings → Integrations → Custom MCP integrations → Add MCP integration. Enter the Telara remote MCP server URL, https://api.telara.dev/v1/mcp. Sana discovers Telara's OAuth server automatically; there is no client secret to paste on either side.
2
Sign in as each user
Sana asks every user to complete the Telara sign-in themselves the first time they use the integration. Telara then applies that user's own policies and consent to every tool call.
3
Verify the connection
From Sana, confirm the integration initializes and lists tools. The tools shown are the ones Telara has granted that user; a shorter list than an admin expects is policy, not a fault.
In Telara
Connect in Telara
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
This catalog entry does not declare extra semantic-search exclusions.
After connect
Verify it worked
This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.
Honesty
Known limitations
This connector runs in one direction only. Sana hosts Telara; Telara does not call a Sana API and holds no Sana credential.
Sana requires automatic OAuth discovery. It cannot be pointed at manually configured OAuth endpoints.