Deputy
Deputy holds the rosters managers publish, the timesheets staff clock against them, leave requests and the sales data many stores feed in for demand-based scheduling. Kept inside Deputy, those records answer scheduling questions. Landed in your own Lake beside POS revenue, payroll and store targets, they show what each shift actually costs against what it earned, location by location.
- Category
- HR & People
- Type
- Workforce scheduling
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0, Access token
- Docs
- Deputy API docs
02Data
What you can sync.
- Rosters
- Timesheets
- Employees
- Leave
- Sales data
Join Deputy rosters with finance and operations for headcount, cost and capacity views in one place.
Need more? Name any other Deputy data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
- An access token
Deputy uses OAuth 2.0 (client ID, client secret, refresh token) or an access token. You add the credentials once, when the AI asks for them, and it tells you where to create them in Deputy if you need help.
04Questions
Questions you can answer.
Once Deputy data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- Which locations run labor above their target percentage of sales, and on which days of the week?
- How far do timesheet hours drift from rostered hours by area and manager?
- Which employees are approaching overtime thresholds before the pay period closes?
- How does approved leave cluster by month, and which teams end up short-staffed as a result?
- Which rosters were built on sales forecasts that missed actual sales by more than 15 percent?
05How it works
How it works in DataMind.
-
Pick Deputy.
Open Lake, pick Deputy in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Deputy API docs.
-
Answer a few questions.
The AI reads the Deputy documentation, then asks which credentials you will use, which data to sync (for example rosters and timesheets), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Deputy data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Pairs
Works well with Deputy.
Sources teams join with Deputy in the Warehouse, each one connected the same way.
-
Square Labor cost from Deputy timesheets against Square sales per hour shows where shifts are over or under covered. - Toast Toast checks by hour next to rostered staff reveal which restaurant shifts are overstaffed for the covers served.
-
Gusto Matching Deputy timesheets to Gusto payrolls confirms that paid hours equal approved hours for every employee.
