View as Markdown
BambooHR icon

BambooHR ACTION

List Clock Entries

List time-tracking clock entries with optional OData filtering. An entry with a null end is still open, so this action also serves to check clocked-in status (filter by employeeId and inspect end). Use returned IDs with Get Clock Entry and Delete Clock Entry. See the documentation
  • Action
  • Read only
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's BambooHR account once, then configure and run List Clock Entries 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-list-clock-entries",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    bamboohr: { authProvisionId: "apn_xxxxxxx" },
    filter: "Filter",
    sort: "Sort",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

List Clock Entries inputs
Property Type Description
filter Filter string
OData filter over timesheetId, employeeId, start, end, e.g. employeeId eq 100.
Optional
sort Sort string
Sort over start, end, updatedAt (default start desc).
Optional
page Page integer
Page number, starting at 1.
Optional
pageSize Page Size integer
Results per page. Min 10, max 200 (default 50).
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-list-clock-entries
Version
0.0.1
App
BambooHR
Authentication
API key
Read-only
Yes
Destructive
No
Open world
Yes