Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tread.ai/llms.txt

Use this file to discover all available pages before exploring further.

Tread syncs bidirectionally with HCSS HeavyJob and Equipment360. Jobs and cost codes flow from HCSS into Tread. Timecards and equipment hours flow back to HCSS for payroll and equipment costing.

​
Prerequisites

  • An active HCSS HeavyJob or Equipment360 subscription.
  • HCSS API credentials, generated at credentials.hcss.com by your HCSS admin.
  • A Tread admin user with the Integrations permission.
  • Scopes: heavyjob:read, heavyjob:write, dis:read, dis:write, e360:timecards:read, e360:timecards:write.

​
How it works

  1. OAuth client credentials — Tread authenticates with HCSS using a client ID and secret.
  2. Pull jobs and cost codes — Tread reads HeavyJob jobs and cost codes on a schedule, plus on-demand resync.
  3. Match employees — HCSS employees map to Tread drivers by external ID.
  4. Push timecards and hours — Approved timesheets post as timecards. Equipment usage posts to Equipment360.
  5. Webhook updates — HCSS pushes job and location updates to Tread in near real time.

​
What flows where

DataDirectionFrequency
JobsHCSS → TreadWebhook + nightly resync
Cost codesHCSS → TreadWebhook + nightly resync
Locations (Setups)HCSS → TreadWebhook
EmployeesHCSS → TreadNightly
TimecardsTread → HCSSOn timesheet approval
Equipment hoursTread → HCSSOn approval

​
Setup

1

Generate HCSS API credentials

Your HCSS admin signs in to credentials.hcss.com and creates a client for Tread with the scopes listed above.
2

Open Integrations settings in Tread

Go to Settings → Integrations → HCSS HeavyJob.
3

Enter the client ID and secret

Paste the credentials. Tread tests the connection and pulls business units.
4

Pick the business unit

Select the HCSS business unit to sync with. Most companies have one.
5

Map employees to drivers

Open each driver in Tread and enter the matching HCSS employee ID in the External ID field.
6

Run the first sync

Trigger an on-demand sync. Confirm jobs and cost codes show on the dispatch board before approving timecards in bulk.

​
Limitations

  • HCSS rate limits Tread to 100 requests per minute, shared across the company.
  • Tread hides HCSS jobs marked inactive or discontinued.
  • Timecard pushes need the HCSS employee ID set on the Tread driver.
  • Cost code edits in Tread do not push back — cost codes are managed in HCSS.
  • Tread does not sync HCSS Safety or Docs modules.

​
Troubleshooting

Authentication failed
  1. Confirm the client ID and secret are pasted exactly — trailing whitespace breaks the token call.
  2. Check that all six scopes are granted on the HCSS client.
Job not on the dispatch board
  1. Check job status in HCSS — inactive jobs hide in Tread.
  2. Trigger a manual sync.
  3. Confirm the job belongs to the selected business unit.
Timecard not posting
  1. Confirm the driver has an HCSS employee ID.
  2. Confirm the job and cost code exist in HCSS and are active.
  3. Use Retry sync on the timesheet.