Zoho People ACTION
Create Attendance Entry
This API can be used to capture the check-in and check-out entries of an individual employee.The system will mark the attendance exit/entry of individual employees.It will automatically update the attendance status in the web portal for every check-in and check-out. See the documentation
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Zoho People account once, then configure and run Create Attendance Entry 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: "zoho_people-create-attendance-entry",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zoho_people: { authProvisionId: "apn_xxxxxxx" },
checkIn: "Check In",
checkOut: "Check Out",
},
})
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": "zoho_people-create-attendance-entry",
"configured_props": {
"zoho_people": { "authProvisionId": "apn_xxxxxxx" },
"checkIn": "Check In",
"checkOut": "Check Out"
}
}'// 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": "zoho_people",
},
},
},
)
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: "zoho_people-create-attendance-entry",
arguments: {
checkIn: "Check In",
checkOut: "Check Out",
},
})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 |
|---|---|---|
checkIn Check In | string | The check in time of the employee. The format should be dd/MM/yyyy HH:mm:ss Required |
checkOut Check Out | string | The check out time of the employee. The format should be dd/MM/yyyy HH:mm:ss Required |
empId Employee ID | string | The employee ID of the employee Optional Dynamic |
emailId Email ID | string | The email ID of the employee Optional |
mapId Map ID | string | The mapper ID of the employee 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
- zoho_people-create-attendance-entry
- Version
- 0.0.2
- App
- Zoho People
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗