Calendly ACTION
List Event Types
Retrieve the event types available to a user or organization via
GET /event_types. Use this to discover valid event type URIs and UUIDs for scheduling flows. Provide either an Organization URI or a User URI; if neither is provided the authenticated user is used. Use List Organization Memberships to find user and organization URIs. Example: called with no props, returns the authenticated user's event types such as { name: "30 Minute Meeting", uuid: "AAAAAAAAAAAAAAAA" } — pass that uuid as the owner prop in Create a Scheduling Link. See the documentation.- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Calendly account once, then configure and run List Event Types 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-list-event-types",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
calendly_v2: { authProvisionId: "apn_xxxxxxx" },
organization: "Organization URI",
user: "User URI",
},
})
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-list-event-types",
"configured_props": {
"calendly_v2": { "authProvisionId": "apn_xxxxxxx" },
"organization": "Organization URI",
"user": "User URI"
}
}'// 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-list-event-types",
arguments: {
organization: "Organization URI",
user: "User URI",
},
})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 |
|---|---|---|
organization Organization URI | string | Organization URI (e.g. https://api.calendly.com/organizations/AAAAAAAAAAAAAAAA). Run List Organization Memberships to find valid organization URIs. Optional |
user User URI | string | User URI (e.g. https://api.calendly.com/users/AAAAAAAAAAAAAAAA). Run List Organization Memberships to find valid user URIs. Optional |
paginate Paginate | boolean | Whether to paginate or not Optional |
maxResults Max Results | integer | Maximum number of results to return (min 1, max 1000). 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
- calendly_v2-list-event-types
- Version
- 0.0.2
- App
- Calendly
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗