Vivocalendar ACTION
Create Appointment
Creates a new appointment. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Vivocalendar account once, then configure and run Create Appointment 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: "vivocalendar-create-appointment",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
vivocalendar: { authProvisionId: "apn_xxxxxxx" },
userId: "User ID",
serviceId: "Service ID",
},
})
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": "vivocalendar-create-appointment",
"configured_props": {
"vivocalendar": { "authProvisionId": "apn_xxxxxxx" },
"userId": "User ID",
"serviceId": "Service ID"
}
}'// 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": "vivocalendar",
},
},
},
)
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: "vivocalendar-create-appointment",
arguments: {
userId: "User ID",
serviceId: "Service ID",
},
})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 |
|---|---|---|
userId User ID | string | The unique identifier for the user Required Dynamic |
serviceId Service ID | string | The unique identifier for the service Required Dynamic |
startTime Appointment Start Time | string | The start time of the appointment. Eg 16:30 Required |
date Appointment Date | string | The date of the appointment. Eg 2024-01-01 Required |
endTime Appointment End Time | string | The end time of the appointment. Eg 17:30 Required |
title Appointment Title | string | The title of the appointment Optional |
price Appointment Price | integer | The price of the appointment Optional |
duration Appointment Duration | integer | The duration of the appointment in minutes Required |
description Appointment Description | string | The description of the appointment Optional |
customerName Customer Name | string | The name of the customer Required |
customerEmail Customer Email | string | The email address of the customer 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
- vivocalendar-create-appointment
- Version
- 0.0.2
- App
- Vivocalendar
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗