LiveKit ACTION
Create Ingress From URL
Create a new ingress from url in LiveKit. See the documentation.
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's LiveKit account once, then configure and run Create Ingress From URL 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: "livekit-create-ingress-from-url",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
livekit: { authProvisionId: "apn_xxxxxxx" },
roomName: "Room Name",
url: "URL",
},
})
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": "livekit-create-ingress-from-url",
"configured_props": {
"livekit": { "authProvisionId": "apn_xxxxxxx" },
"roomName": "Room Name",
"url": "URL"
}
}'// 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": "livekit",
},
},
},
)
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: "livekit-create-ingress-from-url",
arguments: {
roomName: "Room Name",
url: "URL",
},
})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 |
|---|---|---|
roomName Room Name | string | The name of the room to send media to Required Dynamic |
url URL | string | URL of the media to pull for ingresses of type URL Required |
participantIdentity Participant Identity | string | Unique identity of the participant Required |
participantName Participant Name | string | Participant display name Optional |
participantMetadata Participant Metadata | string | Metadata to attach to the participant Optional |
name Ingress Name | string | The name of the ingress Optional |
bypassTranscoding Bypass Transcoding | boolean | Whether to skip transcoding and forward the input media directly. Only supported by WHIP Optional |
enableTranscoding Enable Transcoding | boolean | Whether to enable transcoding or forward the input media directly. Transcoding is required for all input types except WHIP. For WHIP, the default is to not transcode. 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
- livekit-create-ingress-from-url
- Version
- 0.0.3
- App
- LiveKit
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗