Uplisting ACTION
Create Booking
Create a confirmed booking. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Uplisting account once, then configure and run Create Booking 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: "uplisting-create-booking",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
uplisting: { authProvisionId: "apn_xxxxxxx" },
clientId: "X-Uplisting-Client-ID",
checkIn: "Check In",
},
})
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": "uplisting-create-booking",
"configured_props": {
"uplisting": { "authProvisionId": "apn_xxxxxxx" },
"clientId": "X-Uplisting-Client-ID",
"checkIn": "Check In"
}
}'// 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": "uplisting",
},
},
},
)
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: "uplisting-create-booking",
arguments: {
clientId: "X-Uplisting-Client-ID",
checkIn: "Check In",
},
})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 |
|---|---|---|
clientId X-Uplisting-Client-ID | string | Contact Uplisting if you don't have a partner specific client ID. Required |
checkIn Check In | string | The date of the check in. Required |
checkOut Check Out | string | The date of the check out. Required |
propertyId Property Id | string | The id of the property that will be used to the booking. Required Dynamic |
guestName Guest Name | string | Guest name shown on the booking calendar and used for automated messaging. Optional |
guestEmail Guest Email | string | A valid email is required for any scheduled messages to be delivered to the guest. Optional |
guestPhone Guest Phone | string | The guest's phone number. Optional |
numberOfGuests Number Of Guests | integer | Used for price calculation. 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
- uplisting-create-booking
- Version
- 0.0.2
- App
- Uplisting
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗