CONNECT APP
Build with Read AI
Artificial Intelligence (AI)
- OAuth
MCP
Give your agent Read AI tools
Every Read AI action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Read AI account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "read_ai",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Get Meeting:
const result = await mcp.callTool({
name: "read_ai-get-meeting",
arguments: {
meetingId: "Meeting ID",
includeSummary: true,
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "read_ai",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Get Meeting:
result = await session.call_tool("read_ai-get-meeting", {
"meetingId": "Meeting ID",
"includeSummary": True,
})API PROXY
Call the Read AI API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Read AI API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.read.ai/v1/meetings",
})
// Any allowed Read AI endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.read.ai/v1/meetings
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkucmVhZC5haS92MS9tZWV0aW5ncw?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Read AI actions from your backend
Connect a user's Read AI account once, then run Get Meeting on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "read_ai-get-meeting",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
read_ai: { authProvisionId: "apn_xxxxxxx" },
meetingId: "Meeting ID",
includeSummary: true,
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="read_ai-get-meeting",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"read_ai": {"authProvisionId": "apn_xxxxxxx"},
"meetingId": "Meeting ID",
"includeSummary": True,
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "read_ai-get-meeting",
"configured_props": {
"read_ai": { "authProvisionId": "apn_xxxxxxx" },
"meetingId": "Meeting ID",
"includeSummary": true
}
}'TOOLS
Read AI actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Get Meeting
actionRetrieves complete details for a single Read AI meeting, including optional content expansions. Use List Meetings first to find the meeting ID. By default returns only meeting metadata (title, participants, platform, start/end time, duration). Enable specific expansions to include richer content — only request what you need to keep response size manageable:include_summaryfor the AI-generated overview;include_action_itemsfor extracted tasks;include_transcriptfor the full word-for-word transcript with speaker attribution (can be large);include_key_questionsfor AI-flagged discussion questions;include_topicsfor identified subject areas;include_metricsfor speaker engagement data (talk time, interruptions);include_recording_downloadfor a presigned URL to download the meeting recording. See the documentationRead-onlyv0.0.2 -
List Meetings
actionRetrieves a paginated list of meetings from Read AI, ordered by most recent first. Use this to browse meeting history or to find a specific meeting before calling Get Meeting for full details. Supports date range filtering via Unix millisecond timestamps. Returns meeting metadata including ID, title, participants, platform (Zoom/Teams/Google Meet), start time, and duration. Use the expand options to include richer content (summary, action items, transcript, etc.) directly in the listing — note that active meetings will have limited or no data for expanded fields, as these are generated after a meeting concludes. Whenhas_moreistruein the response, pass theidof the last meeting in thedataarray to thecursorparameter to retrieve the next page. To convert a human date to Unix ms, multiply Unix seconds by 1000 (e.g. 7 days ago =Date.now() - 7*24*60*60*1000). See the documentationRead-onlyv0.1.1
EVENTS
Read AI triggers
Event sources your backend can deploy for users and receive through a webhook.
No Read AI triggers are available yet.
- App slug
- read_ai
- Authentication
- OAuth
- Categories
- Artificial Intelligence (AI)
- Actions
- 2
- Triggers
- 0
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Read AI OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- openid
- profile
- meeting:read
- mcp:execute
- offline_access