ProShort AI

1. Install the SDK

   Node.js

   npm install @scalekit-sdk/node

   Python

   pip install scalekit

   Full SDK reference: Node.js | Python

2. Set your credentials

   Add your Scalekit credentials to your .env file. 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>

3. Make your first call

   Node.js

   quickstart.ts

   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   
   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENV_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions
   
   const connector = 'proshortai'
   const identifier = 'user_123'
   
   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'proshortai_recordings_search',
     toolInput: {},
   })
   console.log(result)

   Python

   quickstart.py

   import os
   from scalekit.client import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()
   
   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENV_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions
   
   connection_name = "proshortai"
   identifier = "user_123"
   
   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="proshortai_recordings_search",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)

What you can do

Connect this agent connector to let your agent:

• Search recordings — Search and filter ProShort meeting recordings by title text, date range, attendee email, and conferencing platform
• Get recordings — Retrieve a ProShort recording via the v2 endpoint

Tool list

Use the exact tool names from the Tool list below when you call execute_tool. If you’re not sure which name to use, list the tools available for the current user first.

proshortai_recordings_bulk_get#Fetch details for up to 100 ProShort recordings in one call by their document_ids — e.g. to hydrate a list of results from Search Recordings. Missing/invalid IDs are reported separately in not_found rather than failing the whole request. Use projections to keep the response small when you don't need every field (especially the transcript).2 params▾

Fetch details for up to 100 ProShort recordings in one call by their document_ids — e.g. to hydrate a list of results from Search Recordings. Missing/invalid IDs are reported separately in not_found rather than failing the whole request. Use projections to keep the response small when you don't need every field (especially the transcript).

NameTypeRequiredDescription

meeting_idsarrayrequiredThe document_ids of the recordings to fetch, 1-100 per call. Duplicates are automatically de-duplicated by the API.

projectionsarrayoptionalFields to include for each recording in the response, to minimize payload size. Omit to receive all fields for every recording.

proshortai_recordings_get#Retrieve full detail for a single ProShort meeting recording by its document_id (typically obtained from Search Recordings): title, scheduled time, platform, attendees, prospect company, AI-generated overview, transcript, and media URLs. Use the projections parameter to request only the fields you need and keep the response small — this matters especially for the (potentially large) transcript field.2 params▾

Retrieve full detail for a single ProShort meeting recording by its document_id (typically obtained from Search Recordings): title, scheduled time, platform, attendees, prospect company, AI-generated overview, transcript, and media URLs. Use the projections parameter to request only the fields you need and keep the response small — this matters especially for the (potentially large) transcript field.

NameTypeRequiredDescription

meeting_idstringrequiredThe recording's unique identifier (document_id), e.g. as returned by Search Recordings or Bulk Get Recordings.

projectionsstringoptionalComma-separated list of fields to include in the response, to minimize payload size. Omit to receive all fields. Valid field names: document_id, event_title, source, scheduled_at, meeting_platform, meeting_participants, parties, prospect_company_name, transcript, thumbnail_url, gcp_public_url, overview.

proshortai_recordings_get_v1#Retrieve a ProShort recording via the original v1 endpoint. Unlike the current v3 Get Recording tool (which returns a flattened, plain-text transcript), v1 always returns the complete raw diarized transcript — an array of speaker-attributed segments, each broken into individual words with start/end timestamps and confidence scores — plus meeting participants (with join/leave events) and parties (attendee/company details). There is no field-selection support: v1 always returns every field, with no projections parameter. If the meeting isn't available or doesn't belong to the calling customer, the response still returns HTTP 200 with an empty data object.1 param▾

Retrieve a ProShort recording via the original v1 endpoint. Unlike the current v3 Get Recording tool (which returns a flattened, plain-text transcript), v1 always returns the complete raw diarized transcript — an array of speaker-attributed segments, each broken into individual words with start/end timestamps and confidence scores — plus meeting participants (with join/leave events) and parties (attendee/company details). There is no field-selection support: v1 always returns every field, with no projections parameter. If the meeting isn't available or doesn't belong to the calling customer, the response still returns HTTP 200 with an empty data object.

NameTypeRequiredDescription

meeting_idstringrequiredThe recording's unique identifier (document_id), e.g. as returned by Search Recordings, Bulk Get Recordings, or Get Recording.

proshortai_recordings_get_v2#Retrieve a ProShort recording via the v2 endpoint. The standout difference from the current v3 Get Recording tool: when the overview projection is requested, v2 returns a rich structured object (recap, budget, timing, use_case, pain_points, action_items, prospect_info, contract_status, questions_asked, risks_obstacles, decision_process, customer_reactions, product_discussion, product_experience, product_suggestions, competitors_mentioned) instead of v3's flattened plain-text summary — useful when you need the individual deal-analysis fields rather than prose. Use projections to request only the fields you need; document_id must always be included in the projections list when projections is used. Adding projections is optional but recommended to speed up requests. If the meeting isn't available or doesn't belong to the calling customer, the response still returns HTTP 200 with an empty data object.2 params▾

Retrieve a ProShort recording via the v2 endpoint. The standout difference from the current v3 Get Recording tool: when the overview projection is requested, v2 returns a rich structured object (recap, budget, timing, use_case, pain_points, action_items, prospect_info, contract_status, questions_asked, risks_obstacles, decision_process, customer_reactions, product_discussion, product_experience, product_suggestions, competitors_mentioned) instead of v3's flattened plain-text summary — useful when you need the individual deal-analysis fields rather than prose. Use projections to request only the fields you need; document_id must always be included in the projections list when projections is used. Adding projections is optional but recommended to speed up requests. If the meeting isn't available or doesn't belong to the calling customer, the response still returns HTTP 200 with an empty data object.

NameTypeRequiredDescription

meeting_idstringrequiredThe recording's unique identifier (document_id), e.g. as returned by Search Recordings, Bulk Get Recordings, or Get Recording.

projectionsstringoptionalComma-separated list of fields to include in the response, to minimize payload size and speed up the request. document_id must always be included in this list when projections is used. Omit entirely to receive all fields. Valid field names: document_id, event_title, source, scheduled_at, meeting_platform, meeting_participants, parties, prospect_company_name, transcript, thumbnail_url, gcp_public_url, overview.

proshortai_recordings_search#Search and filter ProShort meeting recordings by title text, date range, attendee email, and conferencing platform. Returns a cursor-paginated list of lightweight recording summaries (document_id, title, scheduled time, platform, participants). Use Get Recording or Bulk Get Recordings afterwards to fetch full details/transcripts for specific results.7 params▾

Search and filter ProShort meeting recordings by title text, date range, attendee email, and conferencing platform. Returns a cursor-paginated list of lightweight recording summaries (document_id, title, scheduled time, platform, participants). Use Get Recording or Bulk Get Recordings afterwards to fetch full details/transcripts for specific results.

NameTypeRequiredDescription

cursorstringoptionalOpaque pagination token from a previous response's next_cursor field. Pass it back exactly as received to fetch the next page; omit it to start from the first page.

from_datestringoptionalLower bound (inclusive) for the meeting's scheduled start time, as an ISO-8601 timestamp.

limitintegeroptionalMaximum number of recordings to return per page. Valid range is 1-100; defaults to 20 if omitted.

participantsarrayoptionalFilter by attendee email address. Provide one or more emails; they are OR-matched (any meeting containing at least one of the given attendees is returned). Matching is case-insensitive. Each value is sent as its own repeated participants query parameter.

platformstringoptionalExact match on the conferencing platform used for the meeting, e.g. zoom, google_meet, teams.

qstringoptionalFree-text search on the meeting title. Supports partial matches. Results are ranked by relevance, then recency.

to_datestringoptionalUpper bound (inclusive) for the meeting's scheduled start time, as an ISO-8601 timestamp.