BambooHR ACTION
Create or Update Hour Records
Bulk add or edit approved hour records in the legacy Hours API. Records whose ID already exists are updated; unrecognized IDs are created. The API can return HTTP 201 even when individual items fail validation — check each item's
success flag in the response. Use Create Hour Record for a single record. 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 or Update Hour Records 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-or-update-hour-records",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
bamboohr: { authProvisionId: "apn_xxxxxxx" },
hourRecords: "Hour Records",
},
})
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-or-update-hour-records",
"configured_props": {
"bamboohr": { "authProvisionId": "apn_xxxxxxx" },
"hourRecords": "Hour Records"
}
}'// 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-or-update-hour-records",
arguments: {
hourRecords: "Hour Records",
},
})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 |
|---|---|---|
hourRecords Hour Records | string | Array of hour record objects as a JSON string. Each item requires timeTrackingId, employeeId, dateHoursWorked (YYYY-MM-DD), hoursWorked, and rateType (REG, OT, or DT); optional fields: divisionId, departmentId, jobTitleId, payCode, payRate, jobCode, jobData. E.g. [{"timeTrackingId":"a1b2c3","employeeId":123,"dateHoursWorked":"2026-09-01","hoursWorked":8,"rateType":"REG"}] Required |
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-or-update-hour-records
- Version
- 0.0.1
- App
- BambooHR
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗