BambooHR ACTION
Create Clock Entry
Create a manual/retroactive clock entry with explicit start and end. For real-time punches use Clock In / Clock Out instead. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's BambooHR account once, then configure and run Create Clock 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: "bamboohr-create-clock-entry",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
bamboohr: { authProvisionId: "apn_xxxxxxx" },
employeeId: "Employee ID",
start: "Start",
},
})
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": "bamboohr-create-clock-entry",
"configured_props": {
"bamboohr": { "authProvisionId": "apn_xxxxxxx" },
"employeeId": "Employee ID",
"start": "Start"
}
}'// 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": "bamboohr",
},
},
},
)
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: "bamboohr-create-clock-entry",
arguments: {
employeeId: "Employee ID",
start: "Start",
},
})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 employee ID (e.g. 100). Run Get Employees Directory to discover IDs. Required |
start Start | string | ISO 8601 datetime for clock-in, e.g. 2026-09-10T09:00:00-05:00. Required |
end End | string | ISO 8601 datetime for clock-out; must be after start, e.g. 2026-09-10T17:00:00-05:00. Required |
timezone Timezone | string | IANA timezone string, e.g. America/Chicago. Required |
note Note | string | Optional note. Optional |
projectId Project ID | string | Optional numeric project ID, e.g. 19. Find valid IDs in your BambooHR time tracking project settings. Optional |
taskId Task ID | string | Optional numeric task ID within the project, e.g. 47 (requires projectId). Find valid IDs in your BambooHR time tracking project settings. Optional |
clockInLocation Clock In Location | string | Optional clock-in location. Optional |
clockOutLocation Clock Out Location | string | Optional clock-out location. 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
- bamboohr-create-clock-entry
- Version
- 0.0.1
- App
- BambooHR
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗