Calendly ACTION
List Event Invitees
List the invitees for a scheduled event via
GET /scheduled_events/{uuid}/invitees. Run List Events first to obtain the event UUID. Example: call with eventId set to a1b2c3d4-e5f6-7890-abcd-ef1234567890 and status set to active to return only that event's non-canceled invitees, each with a uri whose trailing segment is the invitee UUID used by Get Event Invitee and Create Invitee No Show. 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 Invitees 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-invitees",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
calendly_v2: { authProvisionId: "apn_xxxxxxx" },
eventId: "Event UUID",
email: "Inviteee Email",
},
})
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-invitees",
"configured_props": {
"calendly_v2": { "authProvisionId": "apn_xxxxxxx" },
"eventId": "Event UUID",
"email": "Inviteee Email"
}
}'// 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-invitees",
arguments: {
eventId: "Event UUID",
email: "Inviteee Email",
},
})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 |
|---|---|---|
eventId Event UUID | string | The UUID of the scheduled event. Run List Events first to obtain event UUIDs. Required |
email Inviteee Email | string | Indicates if the results should be filtered by email address Optional |
status Event Status | string | Indicates if the invitee canceled or still active 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-invitees
- Version
- 0.0.9
- App
- Calendly
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗