RingCentral ACTION
Make CallOut
Creates a new outbound call out session. See the API docs here
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's RingCentral account once, then configure and run Make CallOut from your backend or agent.
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: "ringcentral-make-callout",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
ringcentral: { authProvisionId: "apn_xxxxxxx" },
accountId: "Account ID",
deviceId: "Device",
},
})
console.log(result)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": "ringcentral-make-callout",
"configured_props": {
"ringcentral": { "authProvisionId": "apn_xxxxxxx" },
"accountId": "Account ID",
"deviceId": "Device"
}
}'// 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": "ringcentral",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "ringcentral-make-callout",
arguments: {
accountId: "Account ID",
deviceId: "Device",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
accountId Account ID | string | Internal identifier of a RingCentral account or tilde ( ~) to indicate the account logged-in within the current session. Required |
deviceId Device | string | Instance id of the caller. It corresponds to the 1st leg of the CallOut call. Required Dynamic |
phoneNumber Phone Number | string | Phone number of the called party. This number corresponds to the 2nd leg of a CallOut call. Phone number in E.164 format. e.g. +16502223366. If you set a Phone Number then don't set an Extension Number. Optional |
extensionNumber Extension Number | string | Extension number of the called party. e.g. ( 103). If you set an Extension Number then don't set a Phone Number. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- ringcentral-make-callout
- Version
- 0.4.2
- App
- RingCentral
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗