Calendly ACTION
Create a Scheduling Link
Creates a single-use scheduling link for an event type via
POST /scheduling_links. Run List Event Types first to obtain the event type UUID. Example: with owner set to https://api.calendly.com/event_types/AAAAAAAAAAAAAAAA's UUID and maxEventCount set to 1, returns a booking URL like https://calendly.com/d/ABC-123/30-minute-meeting that can be scheduled once before expiring. See the documentation- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Calendly account once, then configure and run Create a Scheduling Link 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: "calendly_v2-create-scheduling-link",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
calendly_v2: { authProvisionId: "apn_xxxxxxx" },
owner: "Owner (Event Type UUID)",
maxEventCount: 10,
},
})
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": "calendly_v2-create-scheduling-link",
"configured_props": {
"calendly_v2": { "authProvisionId": "apn_xxxxxxx" },
"owner": "Owner (Event Type UUID)",
"maxEventCount": 10
}
}'// 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": "calendly_v2",
},
},
},
)
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: "calendly_v2-create-scheduling-link",
arguments: {
owner: "Owner (Event Type UUID)",
maxEventCount: 10,
},
})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 |
|---|---|---|
owner Owner (Event Type UUID) | string | The UUID of the event type. Run List Event Types first to obtain event type UUIDs. Required |
maxEventCount Max Event Count | integer | The max number of events that can be scheduled using this scheduling link Required |
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
- calendly_v2-create-scheduling-link
- Version
- 0.1.1
- App
- Calendly
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗