Skip to content
English
  • There are no suggestions because the search field is empty.

πŸ”Œ DASH Connect

Backend 2.88 (November 4, 2025), with follow-on Backend 2.99 (March 18, 2026) | Web Version: Web 2.87 (November 26, 2025)

DASH Connect is the external AI integration and connectivity layer of DASH. It lets external AI tools β€” Claude, ChatGPT, and other LLM clients that support MCP β€” securely interact with SPOTIO on a user's behalf.

The underlying SPOTIO MCP Server originally shipped in late 2025 (Backend 2.88 in November 2025, with the user-facing credential UI on Web 2.87 later that month). The 2026 publication of these release notes reflects the formal grouping of this capability into the DASH suite under the DASH Connect brand, plus continued API/MCP enhancements (Backend 2.99 in March 2026).


What's included in DASH Connect

Originally released in late 2025 β€” now formally part of DASH
  • SPOTIO MCP Server β€” A Model Context Protocol server that exposes SPOTIO capabilities (records, activities, routes, search, actions) to external AI clients in a structured, secure way.
  • Per-user credential management β€” Users configure their MCP connection from Profile Settings, generating credentials scoped to their own SPOTIO permissions. External tools act on behalf of the user, with the same access controls as the SPOTIO UI.
  • Works with major LLM clients β€” Any MCP-compatible client can connect. In practice that includes Claude Desktop, Claude.ai, ChatGPT (via supported clients), and any custom AI workflow that speaks MCP.
  • Read + write capabilities β€” External tools can fetch SPOTIO data (read), and can trigger SPOTIO actions like creating records, scheduling activities, and updating data (write) β€” same actions that DASH itself can perform.

New in 2026 β€” Continued API & MCP Enhancements

  • Adapted API surface (Backend 2.99, March 2026) β€” Internal API and MCP layer refinements that improve consistency between MCP-exposed actions and SPOTIO's first-party API, making external integrations more reliable.


Why this matters in the field

  • SPOTIO works inside the AI tools your team already uses: A sales leader using Claude for daily planning can ask Claude to pull their team's open opportunities, build a route, or schedule follow-ups β€” without leaving Claude.
  • Cross-system workflows: AI agents can combine SPOTIO with Gmail, Slack, calendars, or other connected MCP tools. Example: "Pull every Closed-Lost record from Q1, draft a re-engagement email for each, and queue them in Gmail."
  • Power-user automation without engineering effort: Sales ops and managers can build AI-driven workflows using natural language in their LLM of choice β€” no need to write code against the SPOTIO API directly.
  • Permissions are preserved: External AI tools can only do what the user themselves can do. Admin permissions, record access scopes, and activity permissions all flow through MCP.

Example use cases

 
Scenario What DASH Connect Enables
AI planning session in Claude "Look at my SPOTIO activities for the past two weeks and tell me where I'm under-performing. Suggest a route plan for next week." Claude reads the data via MCP, synthesizes, and the user can have Claude trigger SPOTIO actions to schedule the plan.
Cross-tool automation "Take every Closed-Won record this month, draft a personalized thank-you email referencing their visit notes, and put them in my Gmail drafts." Claude/ChatGPT pulls from SPOTIO via MCP, drafts in Gmail via Gmail MCP.
Manager analysis workflow A manager uses Claude to run weekly analyses across team data β€” without manually exporting CSVs or building dashboards. MCP gives Claude the same data DASH sees.
Custom internal AI agents RevOps teams can build internal agents that combine SPOTIO data with other tools (Salesforce, HubSpot, billing, etc.) through MCP β€” extending SPOTIO into the broader AI stack the company is already adopting.

How to enable / get started

  1. Account must have MCP Server access enabled (contact your CSM or admin if unsure).
  2. User navigates to Profile Settings in the SPOTIO web app to generate MCP credentials.
  3. User configures their MCP-compatible AI client (Claude Desktop, Claude.ai, etc.) with the SPOTIO MCP Server URL and credentials.
  4. External AI tool can now read and write to SPOTIO on the user's behalf, scoped to that user's permissions.

Who this serves

DASH Connect is primarily for the power-user tier of customer orgs:

  • Sales managers and team leads running weekly analysis and planning rituals.
  • RevOps and sales ops teams building cross-system automations.
  • Customers already invested in an AI assistant (Claude, ChatGPT) who want their CRM to participate in that workflow.

Why this is mission critical

 The competitive frame for CRMs is shifting from "best UI" to "most composable into the customer's AI stack." DASH Connect puts SPOTIO ahead of that curve. By exposing field-sales-specific capabilities (records, activities, routes, territory data) through an open MCP server, SPOTIO becomes the field-sales backbone inside the AI tools customers are already standardizing on. This is how SPOTIO stays mission critical as customers' workflows increasingly originate in Claude or ChatGPT rather than in the SPOTIO UI itself β€” the data and the actions still live here, but they're reachable from anywhere.