Deputy

Manage Deputy workforce scheduling from your flows. Agents create employees and scheduled shifts, and pull rosters, timesheets, leave, and locations to sync new hires, publish schedules, and feed reporting.

8 actions API key available

Deputy website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The demand plan for next week arrives from the forecasting sheet

List Employees pulls the active roster for the location, and List Leave flags who is off

Create Roster drafts shifts against each operational unit, unpublished, skipping anyone with approved leave

List Rosters verifies no employee was double-booked across areas

The site manager reviews the draft schedule against the coverage plan and publishes

Each assigned employee gets a direct message with their shift time and location

After the week closes, List Timesheets pulls actual worked hours for payroll

What This Integration Enables

Deputy holds three calendars that constantly disagree: the schedule you planned, the leave you approved, and the hours people actually worked. Most scheduling pain is the manual labor of reconciling them. FlowRunner agents do that reconciliation continuously: they create employees when the HR system hires, draft rosters against operational units with leave already accounted for, pull timesheets with their approval status for payroll, and watch the leave queue so coverage gaps announce themselves early instead of on the morning of. - Sync new hires from [BambooHR](/integrations/bamboohr) into Deputy so scheduling starts on day one - Draft shift schedules from demand plans as unpublished proposals for the manager - Notify assigned employees by [Slack](/integrations/slack) DM when their shifts publish - Pull worked hours per pay period into [Google Sheets](/integrations/google-sheets) for payroll - Email managers a coverage-gap summary via [Gmail](/integrations/gmail) when new leave is approved - Look up employees and locations by search to feed any downstream automation Deputy's structure rewards this: each Company is a location containing operational units, rosters schedule against units, and everything is queryable, which means an agent can reason about coverage per area rather than per building. A restaurant flow can check the kitchen and the floor separately; a clinic flow can distinguish the front desk from the treatment rooms. Coverage logic written at that granularity catches the gaps that a whole-site headcount hides.

Without FlowRunner

The schedule fights the leave calendar Shifts get drafted, then redone when someone notices the approved vacation

Hours reach payroll by re-entry Timesheets get read off one screen and typed into another

Coverage gaps appear on the day An approved leave request quietly leaves Thursday short two people

With FlowRunner

Leave is checked before drafting The agent reads approved leave first, so drafts start from who is actually available

Worked hours flow to the pay sheet Timesheets land in the payroll spreadsheet per pay period, with approval status attached

Gaps surface the moment leave is approved New approved leave triggers a coverage summary to the manager, days ahead

Use Case Scenarios

The hire that never gets scheduled late

A new hire lands in [BambooHR](/integrations/bamboohr). The agent fetches their details, calls Create Employee with their names, contact details, and home location, and confirms the record with Get Employee. Next scheduling cycle, they appear in List Employees like anyone else, and their first shifts go into the manager's draft automatically. The gap where new hires exist in HR but not in scheduling, and therefore never get rostered, closes to zero.

Payroll from timesheets, not transcription

At period close, List Timesheets pulls every record in the date range per employee: start, end, total time, and whether the timesheet is approved. Approved entries append to the payroll tab in [Google Sheets](/integrations/google-sheets). Unapproved entries post to the manager as a checklist, because unapproved time is the thing that makes payroll late. By the time payroll runs, the sheet is complete and every row has been either approved or explicitly chased.

The coverage gap that announces itself

A daily sweep runs List Leave filtered to newly approved requests. For each one, the agent queries List Rosters for that employee's shifts inside the leave window, and any collision becomes an email via [Gmail](/integrations/gmail) to the site manager: who is off, which shifts in which operational unit are now uncovered, and who else on List Employees is qualified for that area and not already rostered. The manager makes the call with a week of runway instead of a morning of scramble.

Human-in-Loop Highlight

Create Roster carries a Published flag, and that single boolean is the difference between a planning document and a commitment on an employee's phone. The moment a roster publishes, a real person plans their week around it: the shift trade they decline, the appointment they move, the childcare they book. An agent that publishes directly, and gets it wrong, spends the team's trust in the schedule itself, which is the one asset a scheduling system cannot operate without. So FlowRunner flows use the flag the way Deputy designed it: agents draft unpublished, having already cross-checked List Leave and List Rosters so the draft is clean, and the site manager reviews the week, "Front bar is drafted at four staff Friday, Priya excluded for approved leave, Marcus is one shift from 40 hours," then publishes. Notifications fan out only after the human has made the schedule a promise worth keeping.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Employees

List Employees Lists employees with optional active-status filtering and text search across names, plus pagination. The roster read behind scheduling drafts, coverage searches, and directory syncs.
Get Employee Retrieves a single employee in full by Deputy Id: names, contact details, employment status, and associated company. The confirmation step after creation and before assignment.
Create Employee Creates a new employee from at minimum a first and last name, with optional contact details and home location. The bridge that turns an HR system hire into a schedulable person.

Rosters

List Rosters Lists scheduled shifts filtered by employee, operational unit, and start-time range. The read behind double-booking checks, coverage collision sweeps, and schedule exports.
Create Roster Creates a scheduled shift for an employee against an operational unit with Unix-timestamp start and end times. Created unpublished by default, which is exactly the draft-then-approve seam FlowRunner builds its human gate on.

Timesheets

List Timesheets Lists recorded worked time filtered by employee and date range, including total time and approval status. The payroll feed, and the source of the unapproved-timesheet chase list.

Locations

List Locations Lists the business's locations as Deputy Company records with Id, name, and address. Reference data for routing employees and rosters to the right site.

Leave

List Leave Lists leave requests filtered by employee and status, with start, end, and leave type. The early-warning feed behind coverage-gap detection.

Frequently Asked Questions

What can FlowRunner do with Deputy?

FlowRunner agents can run List Employees, Get Employee, and Create Employee in Deputy, plus 5 more actions.

Does connecting Deputy to FlowRunner require OAuth?

No. Deputy connects to FlowRunner with an API key, no OAuth flow required.

Can Deputy trigger a FlowRunner workflow automatically?

Deputy doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Deputy

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us