The Chorus connector lets your AI agent act in each user's Chorus account. Each user connects their own Chorus username and password once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 9 tools.
- Tools
- 9
- What they doRead · write · destructive
- 9 · 0 · 09 read0 write0 destructive
- Users sign in with
- Username and password
What you can do
- Read conversations: fetch call and meeting transcripts, participants, tracker matches, and linked CRM accounts or deals
- Search conversations: find calls and meetings by date range, participant, team, tracker, or keyword
- Filter engagements: search calls, meetings, and dialer activity by type, participant, outcome, and date
- Look up users and teams: list and search users and teams, including each team’s members
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Chorus connection
In AgentKit > Connections, create a Chorus connection. The name you give it is the
connection_nameyour code passes. See Configure connections.
Tools
Pass the exact name toexecute_toolchorus_conversation_getRetrieve a single Chorus conversation by ID, including transcript, tracker matches, participants, linked CRM account/deal, recording details, and engagement metrics.Read-onlyGet Conversation
Retrieve a single Chorus conversation by ID, including transcript, tracker matches, participants, linked CRM account/deal, recording details, and engagement metrics.
Inputs
conversation_idstringrequired- Unique identifier of the conversation.
chorus_conversations_listList or search Chorus conversations (calls and meetings), with optional date range, participant, team, and tracker filters.Read-onlyList Conversations
List or search Chorus conversations (calls and meetings), with optional date range, participant, team, and tracker filters.
Inputs
end_datestring- End of the date-time range for filtering conversations (ISO 8601).
page_sizeinteger- Number of results per page.
participant_emailstring- Filter conversations by participant email address.
qstring- Free-text search query.
start_datestring- Start of the date-time range for filtering conversations (ISO 8601).
team_idstring- Filter conversations by team ID.
tracker_namestring- Filter conversations by tracker name.
chorus_engagement_getRetrieve a single Chorus engagement by ID, including type, date, participants, duration, and outcome.Read-onlyGet Engagement
Retrieve a single Chorus engagement by ID, including type, date, participants, duration, and outcome.
Inputs
engagement_idstringrequired- Unique identifier of the engagement.
chorus_engagements_filterSearch Chorus engagements (calls, meetings, and dialer activity) matching the given type, participant, outcome, and date-range criteria.Read-onlyFilter Engagements
Search Chorus engagements (calls, meetings, and dialer activity) matching the given type, participant, outcome, and date-range criteria.
Inputs
end_datestring- End of the date-time range for filtering engagements (ISO 8601).
outcomestring- Filter engagements by outcome.
page_sizeinteger- Number of results per page.
participant_emailsarray- Array of participant email addresses to filter by.
start_datestring- Start of the date-time range for filtering engagements (ISO 8601).
typestring- Filter engagements by type, e.g. MEETING or CALL.
chorus_team_getRetrieve a single Chorus team by ID, including its member list.Read-onlyGet Team
Retrieve a single Chorus team by ID, including its member list.
Inputs
team_idstringrequired- Unique identifier of the team.
chorus_teams_listList teams configured in the Chorus account.Read-onlyList Teams
List teams configured in the Chorus account.
Inputs
page_sizeinteger- Number of results per page.
chorus_user_getRetrieve a single Chorus user by ID.Read-onlyGet User
Retrieve a single Chorus user by ID.
Inputs
user_idstringrequired- Unique identifier of the user.
chorus_users_listList users in the Chorus account, with optional team or role filters.Read-onlyList Users
List users in the Chorus account, with optional team or role filters.
Inputs
page_sizeinteger- Number of results per page.
rolestring- Filter users by role.
team_idstring- Filter users by team ID.
chorus_users_searchSearch Chorus users by free-text query, e.g.Read-onlySearch Users
Search Chorus users by free-text query, e.g. matching name or email.
Inputs
qstringrequired- Free-text search query.
page_sizeinteger- Number of results per page.
No tools match.
Workflows
Proxy API call
const result = await actions.request({ connectionName: 'chorus', identifier: 'user_123', path: '/v1/users/me', method: 'GET',});console.log(result);result = actions.request( connection_name='chorus', identifier='user_123', path="/v1/users/me", method="GET")print(result)Execute a tool
const result = await actions.executeTool({ connector: 'chorus', identifier: 'user_123', toolName: 'chorus_conversations_list', toolInput: {},});console.log(result);result = actions.execute_tool( tool_input={}, tool_name='chorus_conversations_list', connection_name='chorus', identifier='user_123',)print(result)