create procore timecard entries from an external time tracking system so labor hours flow into project budget views
domain: developers.procore.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the company-level Timecard tool is enabled and your integration user has Admin-level permission on it — both are hard prerequisites for creating/updating timecard entries via the API.
Call List Cost Codes and find a cost_code_id whose line_item_types array contains an entry with base_type 'labor'; note that entry's line_item_type_id.
Call Create Timecard Entry (Project) supplying cost_code_id and line_item_type_id from the previous step, along with hours and date.
Use Show / Update / Delete Timecard Entry (Project) to manage individual entries, and Update/Remove Timecard Entry Signature (Project) if a signature needs to be attached or removed.
Create a Timesheet-to-Budget Configuration (referencing the same line_item_type_id) so Timecard Entry Hours becomes available as a source column on a budget view.
Add a budget view source column for Timecard Entry Hours to surface the imported labor hours in project budgets.
Known gotchas
A timecard entry created against a cost_code_id with no 'labor' base_type line item type won't roll up correctly into budget views even though the create call may still succeed.
This path is meant as an alternative to Procore's own Field Productivity product for customers using third-party time tracking, and requires company-level Timecard tool + Admin permission, not just standard project access.
Timecard Entry Hours only becomes visible in a budget view after explicitly creating a Timesheet-to-Budget Configuration — creating timecard entries alone does not surface them in the budget.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?