Nexra
All connectors
Implemented
HR, recruitment & payroll
Deputy logo

Deputy

Read Deputy employees, locations, areas, shifts, timesheets, leave and journals; create employees, shifts, leave and journal notes and update shifts.

Connect workforce scheduling and attendance in Deputy with HRIS, payroll and point-of-sale systems.

Build a flow with DeputyProvider API documentation

Source actions

10

Destination actions

5

Data types

8

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

areas
  • List areas
    Source

    Areas (operational units) within locations.

    areas.list
employees
  • Create employee
    Destination
    Not retried automatically
    Approval before production

    Adds an employee to a location (Management API v2).

    employees.create
  • Get employee
    Source

    One employee by ID.

    employees.get
  • List employees
    Source
    Incremental

    Employees with main location, role and employment dates.

    employees.list
journals
  • Create journal note
    Destination
    Not retried automatically
    Approval before production

    Adds a journal note to an employee.

    journals.create
  • List journals
    Source
    Incremental

    Manager journal notes about employees.

    journals.list
leave rules
  • List leave rules
    Source

    Leave types (rules) such as annual or sick leave.

    leave_rules.list
leave
  • Create leave
    Destination
    Not retried automatically
    Approval before production

    Creates a leave request for an employee, awaiting approval by default.

    leave.create
  • List leave
    Source
    Incremental

    Leave requests with dates, hours, leave rule and status.

    leave.list
locations
  • List locations
    Source

    Locations (Deputy Company records) with address and active flag.

    locations.list
rosters
  • Create shift
    Destination
    Not retried automatically
    Approval before production

    Creates an unpublished shift in an area, assigned or open.

    rosters.create
  • Get shift
    Source

    One rostered shift by ID.

    rosters.get
  • List shifts
    Source
    Incremental

    Rostered shifts with employee, area, times, cost and publish state.

    rosters.list
  • Update shift
    Destination
    Provider duplicate protection
    Approval before production

    Changes a shift's times, area, employee or comment.

    rosters.update
timesheets
  • List timesheets
    Source
    Incremental

    Worked time with start, end, hours, cost and approval (read only).

    timesheets.list

Authentication

Deputy permanent access token

Plans and access

Deputy Premium or Enterprise installs with API access. A permanent token acts as the system administrator who created it and works only for that install.

Test environment

Use a Deputy free trial install for testing.

Rate limits

Deputy does not publish rate limits; Nexra backs off on HTTP 429 and honours Retry-After.

Pagination

Resource QUERY with start and max (up to 500 records), sorted by Id.

Provider events

Deputy webhooks for resource insert, update and delete events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Shifts are created and updated through the Roster resource and are left unpublished; publishing (which notifies employees) is not automated.
  • Timesheets are read only. Clocking employees on or off is not implemented because it changes live attendance.
  • Employees are created with the Management v2 API; updating employees is not implemented because the resource update requires the full record.
  • Leave is created as awaiting approval (Status 0) unless another status is mapped.
  • Field names for Company, OperationalUnit and Timesheet follow Deputy's resource INFO conventions and were not verified on a live install.
  • Dates of birth, gender and pay rates are not mapped. Deletes are not implemented; Deputy has no idempotency key.

Developer reference

  1. Create the Deputy Group Pty Ltd credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Deputy, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Deputy Group Pty Ltd docsAPI referenceDeputy Group Pty Ltd docsAuthentication

Machine-readable detail: GET /api/public/connect/connectors/deputy and the Connections API.