Kenjo ACTION
Create Leave Request
Creates a new leave request in Kenjo. See the documentation.
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Kenjo account once, then configure and run Create Leave Request 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: "kenjo-create-leave-request",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
kenjo: { authProvisionId: "apn_xxxxxxx" },
employeeId: "Employee ID",
timeOffTypeId: "Time Off Type 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": "kenjo-create-leave-request",
"configured_props": {
"kenjo": { "authProvisionId": "apn_xxxxxxx" },
"employeeId": "Employee ID",
"timeOffTypeId": "Time Off Type 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": "kenjo",
},
},
},
)
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: "kenjo-create-leave-request",
arguments: {
employeeId: "Employee ID",
timeOffTypeId: "Time Off Type 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 |
|---|---|---|
employeeId Employee ID | string | The identifier of an employee Required Dynamic |
timeOffTypeId Time Off Type ID | string | The identifier of a time off request type Required Dynamic |
from From | string | The starting date of the time-off request in format YYYY-MM-DD Required |
to To | string | The ending date of the time-off request in format YYYY-MM-DD Required |
partOfDayFrom Part of Day From | string | The duration of the from date. 'StartOfDay' means that the from date is the entire day. 'HalfOfDay' means that the request starts to apply in the middle of the from day. If not specified, the default value will be 'StartOfDay'. Optional |
partOfDayTo Part of Day To | string | The duration of the to date. 'EndOfDay' means that the to date is the entire day. 'HalfOfDay' means the request starts to apply in the middle of the to day. If not specified, the default value will be 'EndOfDay'. Optional |
description Description | string | The description of the time-off request 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
- kenjo-create-leave-request
- Version
- 0.0.2
- App
- Kenjo
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗