Can I use Salesloft as a CLI?

Yes. KosmoKrator exposes a Salesloft CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Salesloft through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Salesloft tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Salesloft credentials stored?

Salesloft credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Salesloft MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

sales

Salesloft CLI for AI Agents

Use the Salesloft CLI from KosmoKrator to call Salesloft tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

6 functions 5 read 1 write Bearer token auth

Submit Salesloft feedback View package source

Salesloft CLI Setup

Salesloft can be configured headlessly with `kosmokrator integrations:configure salesloft`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure salesloft --set access_token="$SALESLOFT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor salesloft --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`access_token`	`SALESLOFT_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`SALESLOFT_URL`	URL `url`	no	API Base URL

Call Salesloft Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call salesloft.salesloft_list_sequences '{
  "limit": 1,
  "page": 1,
  "status": "example_status"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:salesloft salesloft_list_sequences '{
  "limit": 1,
  "page": 1,
  "status": "example_status"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs salesloft --json
kosmo integrations:docs salesloft.salesloft_list_sequences --json
kosmo integrations:schema salesloft.salesloft_list_sequences --json
kosmo integrations:search "Salesloft" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Salesloft.

`salesloft.salesloft_list_sequences`

Read read

List call sequences from Salesloft. Returns sequences with their IDs, names, statuses, and metadata. Supports pagination and optional status filtering.

Parameters: limit, page, status

Generic CLI call

kosmo integrations:call salesloft.salesloft_list_sequences '{"limit":1,"page":1,"status":"example_status"}' --json

Provider shortcut

kosmo integrations:salesloft salesloft_list_sequences '{"limit":1,"page":1,"status":"example_status"}' --json

`salesloft.salesloft_get_sequence`

Read read

Get detailed information about a specific call sequence in Salesloft by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call salesloft.salesloft_get_sequence '{"id":1}' --json

Provider shortcut

kosmo integrations:salesloft salesloft_get_sequence '{"id":1}' --json

`salesloft.salesloft_create_sequence`

Write write

Create a new call sequence in Salesloft with steps, owner assignment, status, and targets.

Parameters: name, steps, owner_id, status, targets

Generic CLI call

kosmo integrations:call salesloft.salesloft_create_sequence '{"name":"example_name","steps":"example_steps","owner_id":1,"status":"example_status","targets":"example_targets"}' --json

Provider shortcut

kosmo integrations:salesloft salesloft_create_sequence '{"name":"example_name","steps":"example_steps","owner_id":1,"status":"example_status","targets":"example_targets"}' --json

`salesloft.salesloft_list_rules`

Read read

List automation rules from Salesloft. Returns rules with their IDs, names, conditions, and actions.

Parameters: limit, page

Generic CLI call

kosmo integrations:call salesloft.salesloft_list_rules '{"limit":1,"page":1}' --json

Provider shortcut

kosmo integrations:salesloft salesloft_list_rules '{"limit":1,"page":1}' --json

`salesloft.salesloft_get_rule`

Read read

Get detailed information about a specific automation rule in Salesloft by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call salesloft.salesloft_get_rule '{"id":1}' --json

Provider shortcut

kosmo integrations:salesloft salesloft_get_rule '{"id":1}' --json

`salesloft.salesloft_get_current_user`

Read read

Get the profile of the currently authenticated Salesloft user. Useful for verifying credentials and identifying the connected account.

Parameters: none

Generic CLI call

kosmo integrations:call salesloft.salesloft_get_current_user '{}' --json

Provider shortcut

kosmo integrations:salesloft salesloft_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`salesloft.salesloft_list_sequences`

List call sequences from Salesloft. Returns sequences with their IDs, names, statuses, and metadata. Supports pagination and optional status filtering.

Operation: Read read
Schema command: kosmo integrations:schema salesloft.salesloft_list_sequences --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of sequences to return per page (default: 25).
`page`	integer	no	Page number for pagination (default: 1).
`status`	string	no	Filter sequences by status (e.g., "active", "paused").

`salesloft.salesloft_get_sequence`

Get detailed information about a specific call sequence in Salesloft by its ID.

Operation: Read read
Schema command: kosmo integrations:schema salesloft.salesloft_get_sequence --json

Parameter	Type	Required	Description
`id`	integer	yes	The sequence ID.

`salesloft.salesloft_create_sequence`

Create a new call sequence in Salesloft with steps, owner assignment, status, and targets.

Operation: Write write
Schema command: kosmo integrations:schema salesloft.salesloft_create_sequence --json

Parameter	Type	Required	Description
`name`	string	yes	Name of the call sequence.
`steps`	array	no	Array of step definitions for the sequence. Each step defines an action (e.g., call, email).
`owner_id`	integer	no	ID of the user who will own this sequence.
`status`	string	no	Initial status of the sequence (e.g., "active", "paused").
`targets`	array	no	Array of target people or account IDs to add to the sequence.

`salesloft.salesloft_list_rules`

List automation rules from Salesloft. Returns rules with their IDs, names, conditions, and actions.

Operation: Read read
Schema command: kosmo integrations:schema salesloft.salesloft_list_rules --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of rules to return per page (default: 25).
`page`	integer	no	Page number for pagination (default: 1).

`salesloft.salesloft_get_rule`

Get detailed information about a specific automation rule in Salesloft by its ID.

Operation: Read read
Schema command: kosmo integrations:schema salesloft.salesloft_get_rule --json

Parameter	Type	Required	Description
`id`	integer	yes	The rule ID.

`salesloft.salesloft_get_current_user`

Get the profile of the currently authenticated Salesloft user. Useful for verifying credentials and identifying the connected account.

Operation: Read read
Schema command: kosmo integrations:schema salesloft.salesloft_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.