Platform Integration
Workforce Management

Deputy

Integrate Deputy with your critical business systems to sync employee data, schedules, and timesheets. Eliminate manual data entry, reduce errors, and ensure operational consistency across your entire organization.

Connect Deputy with your tech stack to automate workforce management.

Deputy provides a unified solution for workforce management, including scheduling, time and attendance, and task management. By integrating Deputy through Flows360, you can connect its capabilities to the rest of your software stack. Automate employee onboarding by syncing new hire data from your HRIS directly into Deputy. Streamline payroll by pushing approved timesheets to your finance or ERP system. Align workforce schedules with business objectives by connecting Deputy to your project management platform. This integration breaks down data silos, reduces administrative overhead, and provides a real-time, comprehensive view of your operations.

Common use cases

  • Automated Employee Onboarding
  • Streamlined Payroll and Invoicing
  • Unified Workforce and Project Planning
  • Centralized Time and Attendance Tracking

Sync scenarios

  • Sync new hires from HR platforms to Deputy user profiles.
  • Push approved timesheets from Deputy to payroll systems.
  • Update project tasks with assigned staff from Deputy schedules.
  • Import employee leave balances from HRIS into Deputy.

Objects supported

  • Employee
  • Roster
  • Timesheet
  • Leave
  • Journal
  • Task

Actions

  • get_employee
  • create_employee
  • update_employee
  • delete_employee
  • get_roster
  • create_roster
  • update_roster
  • delete_roster
  • get_timesheet
  • create_timesheet
  • update_timesheet
  • get_leave
  • create_leave
  • approve_leave
  • new_timesheet_entry
  • roster_published
  • employee_created

Frequently asked questions

What data can I sync with the Deputy integration?

You can sync employee records, schedules, timesheets, leave requests, and task assignments between Deputy and other applications.

How does connecting Deputy help with payroll?

You can configure the integration to automatically push approved timesheet data from Deputy directly to your payroll system, which ensures accurate, on-time payments and reduces manual processing.

Can I use this integration to automate employee onboarding?

Yes. When a new employee is added to your primary HR system, their data can be automatically synced to create a new user profile in Deputy, streamlining the onboarding process.

  • Auth method: OAuth 2.0
  • Required scopes: 7
  • Supported objects: 6
  • Supported actions: 17

Overview

Deputy provides a unified solution for workforce management, including scheduling, time and attendance, and task management. By integrating Deputy through Flows360, you can connect its capabilities to the rest of your software stack.

Key operations enabled by this integration include:
* Automated Employee Onboarding: Sync new hire data from your HRIS directly into Deputy, ensuring employee records are consistent and up-to-date from day one.
* Streamlined Payroll Processing: Push approved timesheets from Deputy to your finance or ERP system, eliminating manual data entry and reducing payroll errors.
* Aligned Workforce Scheduling: Connect Deputy to your project management platform to align workforce schedules with specific business objectives and project timelines.

This integration breaks down data silos between your workforce management and other critical business systems, reduces administrative overhead, and provides a real-time, comprehensive view of your operations.

Setup steps

1. Navigate to the "Connections" page in the Flows360 admin panel.
2. Click "Add Connection" and select "Deputy" from the list of available providers.
3. Click "Connect" to be redirected to the Deputy authorization screen.
4. Enter your Deputy account credentials to log in.
5. Review the requested permissions and grant access to allow Flows360 to interact with your Deputy data.
6. You will be redirected back to Flows360. Name your connection for easy identification and click "Save".

Required scopes

  • user.read
  • roster.read
  • roster.write
  • timesheet.read
  • timesheet.write
  • leave.read
  • leave.write

Supported objects

  • Employee
  • Roster
  • Timesheet
  • Leave
  • Journal
  • Task

Supported actions

  • get_employee — Retrieves a specific employee by their ID.
  • create_employee — Creates a new employee record in Deputy.
  • update_employee — Updates an existing employee's record.
  • delete_employee — Deletes an employee record from Deputy.
  • get_roster — Fetches the details of a specific roster (schedule).
  • create_roster — Creates a new roster.
  • update_roster — Updates an existing roster.
  • delete_roster — Deletes a roster.
  • get_timesheet — Retrieves a specific timesheet by its ID.
  • create_timesheet — Creates a new timesheet entry.
  • update_timesheet — Updates an existing timesheet entry.
  • get_leave — Retrieves leave request details.
  • create_leave — Submits a new leave request.
  • approve_leave — Approves a pending leave request.
  • new_timesheet_entry — Triggered when a new timesheet is submitted.
  • roster_published — Triggered when a new roster is published.
  • employee_created — Triggered when a new employee is created.

Use cases

  • Revenue Operations
  • Finance & Billing
  • HR & People Ops

Limitations

* API Rate Limits: The Deputy API is subject to rate limiting. High-volume data synchronization flows may encounter these limits. Implement retry logic with exponential backoff for robust error handling.
* Webhook Event Delivery: While webhook notifications for events like `roster_published` are generally delivered in near-real-time, network latency can introduce minor delays.
* Data Consistency: Data reflects the state at the time of the API call. For real-time data needs, rely on webhook-triggered flows rather than scheduled polling.
* Object Deletion: The `delete_employee` and `delete_roster` actions permanently remove data from Deputy. These operations are irreversible and should be used with caution.

Troubleshooting

Why am I receiving a "401 Unauthorized" or "Invalid Credentials" error?
My flow is running successfully, but data isn't appearing in Deputy (or vice versa). What should I do?
I am encountering a "Rate Limit Exceeded" error. How can I resolve this?

Start your structured rollout today.

Don’t leave your orchestration to chance. Implement the governance engine used by disciplined operational teams worldwide.

Deploy Flows360 Book a Demo →