Calendly ACTION
Get Event Invitee
Retrieve the full invitee resource (including
email, name, status, reschedule_url, and no_show) via GET /scheduled_events/{event_uuid}/invitees/{invitee_uuid}. Use the returned reschedule_url to direct an invitee to self-reschedule. Run List Events to find event UUIDs, then List Event Invitees to find invitee UUIDs. Example: with eventUuid set to a1b2c3d4-e5f6-7890-abcd-ef1234567890 and inviteeUuid set to f7e6d5c4-b3a2-1098-fedc-ba9876543210, returns that invitee's email, name, and status: "active". See the documentation.- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Calendly account once, then configure and run Get Event Invitee 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-get-invitee",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
calendly_v2: { authProvisionId: "apn_xxxxxxx" },
eventUuid: "Event UUID",
inviteeUuid: "Invitee UUID",
},
})
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-get-invitee",
"configured_props": {
"calendly_v2": { "authProvisionId": "apn_xxxxxxx" },
"eventUuid": "Event UUID",
"inviteeUuid": "Invitee UUID"
}
}'// 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-get-invitee",
arguments: {
eventUuid: "Event UUID",
inviteeUuid: "Invitee UUID",
},
})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 |
|---|---|---|
eventUuid Event UUID | string | The UUID of the scheduled event (the {event_uuid} path segment, e.g. a1b2c3d4-e5f6-7890-abcd-ef1234567890). Run List Events first to obtain event UUIDs. Required |
inviteeUuid Invitee UUID | string | The UUID of the invitee within that event (the {invitee_uuid} path segment, e.g. f7e6d5c4-b3a2-1098-fedc-ba9876543210). The invitee list is returned by List Event Invitees. 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-get-invitee
- Version
- 0.0.2
- App
- Calendly
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗