Overview
The Salesloft integration lets users connect their Salesloft workspace so Alysio can list and query people, accounts, cadences, calls, tasks, and emails on their behalf. Users can ask Alysio to find people or accounts, see person and account stages, list cadences and cadence memberships, view call activity, tasks, and email outreach—all in natural language. The integration uses the user’s connected Salesloft credential and is read-only (list endpoints only); it does not create, update, or delete records in Salesloft. Results can be paginated (e.g. per_page up to 1000, page 1, 2, 3…).
Supported capabilities / objects
- People — List people with filtering, sorting, and pagination; person stages (names and IDs). Person stage and user IDs in results can be resolved to names using the list stages and list users tools.
- Accounts — List accounts with name/domain filtering, sorting, and pagination; account (company) stages.
- Users — List users in the Salesloft organization (for resolving owner/creator IDs in other lists).
- Cadences — List cadences with filtering and pagination; list cadence memberships (who is enrolled in which cadence). Cadence and user IDs can be resolved to names.
- Calls — List call activity with sorting and pagination (duration, sentiment, disposition, contacts).
- Tasks — List tasks with sorting and pagination (subject, state, due dates, contacts).
- Emails — List emails with filtering by sender, recipient, cadence, date range, status, and direction; pagination. Use list_people for person_id and list_users for user_id when filtering.
Authentication
Method: OAuth 2.0 (Salesloft). The MCP sends requests using a Bearer token and a credential ID that identifies the user’s connected Salesloft account. Requests are sent to the Salesloft API (https://api.salesloft.com/v2).
Redirect URI: Configured when the Salesloft integration is set up in Alysio. The Salesloft OAuth app must allow this redirect URI.
Token handling
- OAuth tokens for the connected Salesloft account are stored securely and refreshed automatically.
- Each user/tenant has their own credential; the MCP sends the appropriate credential ID with each request so calls are isolated per connection.
- On disconnect, that credential is no longer used and Salesloft tools will not be available for that user until they reconnect Salesloft.
Required scopes
people.readpeople.writecalls.readcalls.writetasks.readtasks.writeaccounts.read
Connection required: Users must connect Salesloft in Alysio before Salesloft tools work. If the connection is missing or expired, they may need to re-authorize in Settings → Integrations.
Filtering and pagination: For email filtering by sender or recipient, use user_id (from salesloft_list_users) and person_id (from salesloft_list_people). Pagination: use per_page (max 1000) and page for more results.
The Salesloft MCP exposes the following tools. Users can invoke these capabilities through natural language in Alysio.
| Tool | Description | Example user prompts |
|---|
salesloft_list_people | Lists people with filtering, sorting, and pagination; returns contact details, stages, and engagement; person stage IDs can be resolved via list_person_stages. | ”List people in our Salesloft”, “Find contacts by stage.” |
salesloft_list_person_stages | Lists person stages (names, IDs) with sorting and pagination. | ”What person stages do we have?”, “List person stages.” |
salesloft_list_calls | Lists call activity with sorting and pagination (duration, sentiment, disposition, contacts). | ”List calls from last week”, “Show call activity.” |
salesloft_list_tasks | Lists tasks with sorting and pagination (subject, state, due date, contacts). | ”List my tasks”, “Show overdue tasks.” |
salesloft_list_users | Lists users in the Salesloft organization (for resolving user IDs in people, cadences, emails). | ”List Salesloft users”, “Who are our users?” |
salesloft_list_accounts | Lists accounts with optional name/domain filter, sorting, and pagination; company stage IDs can be resolved via list_account_stages. | ”Find accounts by domain salesloft.com”, “List accounts by name.” |
salesloft_list_account_stages | Lists account (company) stages (names, IDs) with sorting and pagination. | ”What account stages do we have?”, “List company stages.” |
salesloft_list_cadences | Lists cadences with filtering, sorting, and pagination (enrollment counts, owner, status). | ”List our cadences”, “Which cadences are active?” |
salesloft_list_cadence_memberships | Lists cadence memberships (person–cadence relationships, enrollment status) with filtering and pagination. | ”Who is enrolled in this cadence?”, “List cadence memberships.” |
salesloft_list_emails | Lists emails with filtering by sender (user_id), recipient (person_id), cadence, date range, status, direction, and pagination. | ”Emails sent to this contact”, “List emails from last month.” |
App Behavior
- API calls are made on-demand only when the user asks something that requires Salesloft data (e.g. list people, accounts, cadences, calls, tasks, emails). There is no background sync; each request triggers the relevant Salesloft API call using the user’s OAuth credential. Some list tools automatically resolve stage or user IDs to names by calling other list endpoints when needed.
Example flow
- User asks: “Who is enrolled in our Q1 outreach cadence?”
- Alysio routes the request to the Salesloft MCP.
- The MCP may call
salesloft_list_cadences to find the cadence ID, then salesloft_list_cadence_memberships filtered by that cadence; it may also resolve cadence/person/user IDs to names for display.
- The request is sent to the Salesloft API using the user’s stored OAuth credential.
- The MCP returns the membership list (and name mappings); Alysio presents the answer in chat.
Troubleshooting
Common issues
- Missing or expired connection — User sees errors or no Salesloft data. Fix: Reconnect Salesloft in Settings → Integrations (re-authorize with Salesloft).
- 401 Unauthorized — Token invalid or expired. Fix: Re-authorize the integration in Settings → Integrations.
- 403 Forbidden — Insufficient OAuth scopes. Fix: Ensure the Salesloft OAuth app has read scopes for the endpoints you use (people, accounts, cadences, calls, tasks, emails, users, stages).
- Empty or partial results — Filters or pagination may limit results. Fix: Widen filters or use a higher per_page (max 1000) and additional pages (page=2, 3, …).
- IDs in response instead of names — Some responses include stage or user IDs; the tool output may include a mapping table. Fix: Use the provided mapping in the response, or call salesloft_list_person_stages / salesloft_list_account_stages / salesloft_list_users to resolve IDs to names.
Support
