Resources · Make integration

Deputy Make integrationAutomate Deputy with Make.

Can Make react the moment something changes in Deputy? Yes. The Deputy Make integration gives you 53 modules, including 12 instant triggers. This guide is for ops and HR teams: connect your account, build a first scenario, then pick the right module.

Try the Deputy integration on Make See the 53 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Deputy Make integration let you automate?

The Deputy Make integration links your Deputy workforce account to Make, a no-code tool where you build a scenario: a chain of modules that runs by itself. Deputy sends Make an event (a new hire, a leave request, a saved timesheet) and the next modules act on staff, rosters, locations or timesheets for you.

Onboarding that starts on its own. Watch New Employees fires when someone joins, and Create a Task hands the manager the first steps. Add Invite an Employee and the new hire gets access without a separate reminder.

Leave requests that reach the right people. Watch New Leave Requests catches each request as it is submitted. From there, a scenario can pass the details to another app your team already reads, or post a note with Create a News Feed.

Timesheets that close cleanly. Watch Timesheets Updates reacts when an entry changes, Approve a Timesheet signs it off, and Update or Create a Timesheet fixes a missing one. Payroll prep stops depending on someone scrolling through every entry.

Know the limits before you start. Every Deputy trigger is instant, so there is no clock to set on them, and the official Make documentation for Deputy is marked as AI-generated from Deputy's own docs, so check key details on a test account. When a listed module falls short, Make an API Call reaches the rest of the Deputy API with the same connection.

Deputy may also have an n8n node; our n8n vs Make page lays out how the two tools differ. To judge Make itself first, read the Make review, and if you want a guided start, the Make training walks through scenarios step by step.

Connect

How do you connect Deputy to Make?

01
Add a Deputy module
Open a scenario, click the +, search for Deputy and pick a module. Click Create a connection. A connection is your Deputy account linked to Make once, then reused by every Deputy module. With an instant trigger, click Create a webhook first.
02
Name the connection
The Connection name field is optional, but a clear name pays off once you manage several Deputy accounts or environments. Something like the business name plus the word test or live tells your teammates which one a scenario uses.
03
Paste your Deputy credentials
You need an active Deputy account. In Deputy, open the OAuth clients section, click New OAuth Client, set the callback URI to https://www.integromat.com/oauth/cb/deputy and save. Copy the Client ID and Client secret into Make, then follow the on-screen steps.

First scenario

Your first scenario: a task for each new hire

GoalWhen a new employee is created in Deputy, Make adds an onboarding task in Deputy.

01
Start a new scenario
From the Scenarios page, create a new scenario and click the big +. Search for Deputy and choose Watch New Employees as the first module, the one that starts everything.
02
Hook up the webhook
Because this trigger is instant, click Create a webhook, then Create a connection with the OAuth credentials from your Deputy account. From now on, Deputy tells Make whenever a new employee record appears.
03
Add the onboarding task
Click the + to the right of the trigger and add Create a Task. Fill the fields Make shows, and map the employee data from the trigger so the manager knows who the task is for.
04
Test with Run once
Click Run once, then add a test employee in Deputy. Each module shows the bundles it received: a bundle is one item passed along, here one employee. Check that the task points to the right person.
05
Switch it on
Save the scenario and turn it on. There is no interval to pick with an instant trigger: Make waits for Deputy's call and runs one pass for each new hire, counting an operation per module executed.

Triggers

Deputy triggers: what starts a scenario

12 modules start a scenario when something happens in Deputy. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Deputy as soon as it happens.

Deputy1Watch Employees Deletion

Watch Employees Deletion

Instant trigger

In Make“Triggers when an employee has been deleted.”

This trigger tells your scenario that an employee record is gone from Deputy, so the people data you keep elsewhere does not keep a ghost on the payroll list or in the staff directory.

How it fires

instant. Deputy calls Make through a webhook as soon as the deletion happens, so there is no schedule to set on this module.

When to use it

you mirror your staff list in a spreadsheet or an HR tool and want the row archived as soon as someone is removed from Deputy.

Watch out

the employee is already gone from Deputy, so take what you need from the trigger bundle itself rather than planning a Get an Employee lookup afterwards.

Deputy2Watch Employees Updates

Watch Employees Updates

Instant trigger

In Make“Triggers when an employee has been updated.”

Whenever someone edits an employee profile in Deputy, this module hands the updated record to your scenario, so the other tools that hold staff details can catch up without a manual copy.

How it fires

instant. Deputy calls Make through a webhook as soon as the update is saved.

When to use it

a manager changes a phone number or a role in Deputy and your HR file or team chat directory should show the same thing.

Watch out

if the same scenario later runs Update an Employee on that person, Deputy can send a fresh update event and the scenario may call itself again. Keep the write-back in another scenario or add a filter.

Deputy3Watch New Area/Departments

Watch New Area/Departments

Instant trigger

In Make“Triggers when a new area or department has been created.”

Opening a new area or department in Deputy becomes a signal your other systems can act on, which saves you from creating the same team structure by hand in each tool.

How it fires

instant. Deputy calls Make through a webhook the moment the area or department is created.

When to use it

a restaurant adds a terrace section or a clinic opens a new ward, and the matching channel, cost center or list should appear elsewhere.

Watch out

only creations count here. Renaming or removing an area does not start this scenario, so plan another route for those changes.

Deputy4Watch New Comments

Watch New Comments

Instant trigger

In Make“Triggers when a comment has been added.”

Each comment added in Deputy lands in your scenario, which means a remark left on a shift or a post can reach people who never open Deputy during the day.

How it fires

instant. Deputy calls Make through a webhook as soon as the comment is added.

When to use it

a team lead wants replies to the news feed or shift notes copied into the channel where decisions are actually taken.

Watch out

busy teams comment a lot, and every comment is a run that spends operations. Add a filter right after the trigger so only the comments you care about move on.

Deputy5Watch New Employees

Watch New Employees

Instant trigger

In Make“Triggers when a new employee has been created.”

The moment a new staff member exists in Deputy, this trigger passes their record to Make. It is the natural starting point for any onboarding flow you want to stop doing by hand.

How it fires

instant. Deputy calls Make through a webhook as soon as the employee is created.

When to use it

a new hire should get a welcome task, an invitation to the app, and a line in your HR tracker without anyone remembering to do it.

Watch out

an employee created by a Make scenario also fires this trigger. If a scenario creates staff, keep it away from the one listening here.

Deputy6Watch New Leave Requests

Watch New Leave Requests

Instant trigger

In Make“Triggers when a new leave request has been submitted.”

Every leave request submitted in Deputy reaches your scenario straight away, so the manager who approves it and the planner who covers the gap hear about it at the same time.

How it fires

instant. Deputy calls Make through a webhook as soon as the request is submitted.

When to use it

requests pile up unseen inside Deputy and you want each one pushed to the approver's inbox or logged in a shared absence sheet.

Watch out

this fires on submission, not on approval. Word your message as a request, never as confirmed time off.

Deputy7Watch New Schedules

Watch New Schedules

Instant trigger

In Make“Triggers when a new schedule has been added.”

A schedule added in Deputy (a roster entry, in Deputy's own words) starts your scenario with its details, which lets you echo new shifts wherever your staff actually look.

How it fires

instant. Deputy calls Make through a webhook as soon as the schedule is added.

When to use it

part-timers live in a group chat or a shared calendar and should see a new shift there instead of hunting for it in the app.

Watch out

a scenario that runs Create a Schedule will also trigger this module. Split creation and notification into separate scenarios.

Deputy8Watch News Feed Deletion

Watch News Feed Deletion

Instant trigger

In Make“Triggers when an announcement has been deleted.”

When an announcement disappears from the Deputy news feed, this trigger lets your scenario take the copy down elsewhere, so outdated notices do not linger in other channels.

How it fires

instant. Deputy calls Make through a webhook as soon as the announcement is deleted.

When to use it

you already mirror announcements to a chat channel or intranet page and want removals mirrored too.

Watch out

to delete the matching copy, your first scenario needs to have stored a link between the Deputy announcement and the message it created, for instance in a data store or a sheet.

Deputy9Watch New Timesheets

Watch New Timesheets

Instant trigger

In Make“Triggers when a new timesheet has been saved.”

Each timesheet saved in Deputy flows into Make as it is recorded, giving you a live feed of worked hours to check, total or send toward payroll.

How it fires

instant. Deputy calls Make through a webhook as soon as the timesheet is saved.

When to use it

your payroll or project tracker needs a line per worked shift, and retyping hours from Deputy is where the errors creep in.

Watch out

a new timesheet can still be edited or approved later. Pair this with Watch Timesheets Updates if the numbers you send must be final.

Deputy10Watch Schedules Deletion

Watch Schedules Deletion

Instant trigger

In Make“Triggers when a schedule has been deleted.”

This trigger warns your scenario when a schedule is removed in Deputy, so a cancelled shift does not stay alive in someone's calendar or in a coverage sheet.

How it fires

instant. Deputy calls Make through a webhook as soon as the schedule is deleted.

When to use it

you copy shifts to external calendars and a cancellation should free that slot for the staff member right away.

Watch out

Delete a Schedule run by another scenario also lands here, which is fine for a cleanup flow but can surprise you if you only expected manual cancellations.

Deputy11Watch Schedules Updates

Watch Schedules Updates

Instant trigger

In Make“Triggers when a schedule has been updated.”

A shift moved, extended or reassigned in Deputy is pushed to your scenario with its new details, so every copy of the roster can follow the change.

How it fires

instant. Deputy calls Make through a webhook as soon as the schedule is updated.

When to use it

staff rely on a calendar or a message rather than the app, and a late change to their shift must reach them without a phone call.

Watch out

Update a Schedule or Publish a Schedule in the same scenario can send a fresh update back and restart the flow. Keep writes and alerts apart.

Deputy12Watch Timesheets Updates

Watch Timesheets Updates

Instant trigger

In Make“Triggers when a timesheet has been updated.”

When a timesheet changes in Deputy, whether someone corrects hours or a manager signs it off, your scenario receives the new version and can refresh the numbers downstream.

How it fires

instant. Deputy calls Make through a webhook as soon as the timesheet is updated.

When to use it

your payroll export should always carry the latest hours, not the first draft captured at clock-out.

Watch out

Approve a Timesheet, Pause / Unpause a Timesheet and Update or Create a Timesheet all change timesheets. If a scenario runs them after this trigger, it can trigger itself again.

Modules

What Deputy can do in Make

Deputy gives you 41 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Deputy1

Activate a Terminated Employee

Action

In Make“Activates a terminated employee.”

Bring a former staff member back to active status in Deputy, so a returning seasonal worker can be rostered again without a brand new profile and a lost history.

When to use it

your hiring tool marks a rehire, and the scenario reactivates the matching Deputy record instead of creating a duplicate.

Watch out

it only works on terminated employees; a deleted record cannot come back this way.

Deputy2

Approve a Timesheet

Action

In Make“Approves a timesheet.”

Signs off a timesheet in Deputy for you, which removes the click-by-click approval round that managers usually leave until payroll day.

When to use it

hours that match the planned shift can be approved automatically once a filter has compared them, leaving only the odd ones for a human.

Watch out

approval is a real decision. Put a filter before this module and test on a demo timesheet with Run once before switching the scenario on.

Deputy3

Create a Location

Action

In Make“Creates a new location (workplace / company).”

Adds a new workplace to Deputy (Deputy calls it a location, and sometimes a company), giving a new site its own place for staff and rosters without a trip through the settings.

When to use it

a franchise signs a new store in your CRM and the site should exist in Deputy before the first hires arrive.

Watch out

each run creates a site. Check your existing ones with List My Locations first if the source could send the same store twice.

Deputy4

Create an Area / Department

Action

In Make“Creates an area / department.”

Opens a new area or department in Deputy, the unit your shifts are planned on, so the structure of a site grows as your operations grow.

When to use it

a new service line (a click-and-collect desk, a night team) is approved elsewhere and needs its own roster section in Deputy.

Watch out

Watch New Area/Departments fires on what this module creates, so do not let both sit in one scenario.

Deputy5

Create an Employee

Action

In Make“Creates a new staff member.”

Creates a staff member in Deputy from data you already have, sparing HR from typing the same details twice when someone signs their contract.

When to use it

a candidate moves to Hired in your recruiting tool and should appear in Deputy ready to be rostered.

Watch out

inviting is a separate module. Add Invite an Employee after it when the person must log in, and keep this away from any scenario watching new employees.

Deputy6

Create a News Feed

Action

In Make“Creates a news feed announcement.”

Posts an announcement to the Deputy news feed, the place frontline staff already check between shifts, so your message reaches them without another app.

When to use it

a policy is published in your document tool, or a store closes early, and the team should read it in Deputy.

Watch out

each run posts again. If the source can send the same item twice, add a filter or you will stack identical announcements.

Deputy7

Create a Schedule

Action

In Make“Creates a new schedule / roster.”

Adds a shift to Deputy's roster from another source, which is how bookings or forecasts can turn into planned hours without copying them across.

When to use it

an event is confirmed in your booking tool and the extra staff it needs should appear as draft shifts for the planner.

Watch out

publishing is its own module. Follow with Publish a Schedule once you are sure the shift is right.

Deputy8

Create a Task

Action

In Make“Creates a new task.”

Drops a task into Deputy for a staff member or a manager, turning an event anywhere in your stack into a to-do people see where they already work.

When to use it

a new hire arrives, a delivery is logged or an audit is due, and someone on site must act on it during their shift.

Watch out

keep task text short and mapped from the trigger. A generic title repeated on every run makes the list impossible to read.

Deputy9

Create / Update a Journal

Action

In Make“Creates or updates a journal.”

Writes a journal entry in Deputy, or updates an existing one, so notes about an employee sit next to their shifts instead of in a forgotten document.

When to use it

a form filled after a review or an incident should leave a trace on the person's Deputy file.

Watch out

since the module can also update, check with Run once that it touches the entry you meant rather than writing a new one each time.

Deputy10

Delete a Discarded Employee

Action

In Make“Deletes a discarded / terminated employee's account in Deputy.”

Removes the account of an employee who has already been discarded or terminated in Deputy, clearing out records you no longer need to keep.

When to use it

a cleanup scenario deletes old profiles once your offboarding checklist in another tool is marked complete.

Watch out

it only acts on someone already discarded or terminated, so Terminate an Employee comes first. Activate a Terminated Employee brings back a terminated person, not a deleted one.

Deputy11

Delete a Location

Action

In Make“Deletes a location in Deputy after migrating associated employees to another location.”

Closes a location in Deputy for good after its employees have been moved to another location, which keeps the account tidy when a site shuts down.

When to use it

a store closure is confirmed in your CRM or project tool and the Deputy site should go once its staff have a new home.

Watch out

the staff migration is part of the job, so decide the destination location first and test the whole thing on a spare site.

Deputy12

Delete a Schedule

Action

In Make“Discards a schedule.”

Discards a shift in Deputy, so a cancelled booking or a closed day stops showing up as planned work for the person rostered on it.

When to use it

a client cancels a job in your booking system and the matching Deputy shift should vanish without the planner stepping in.

Watch out

the scenario has to know which shift to remove. Keep a reference when the shift is created, or find it with List Schedules, before deleting.

Deputy13

End a Timesheet

Action

In Make“Ends a shift that is in progress.”

Stops a shift that is still running in Deputy, closing the timesheet that was left open when someone forgot to clock out.

When to use it

a door badge system or a point-of-sale close tells you the site is shut, and any open timesheet should end with it.

Watch out

it acts only on a shift in progress. If the person has already clocked out, there is nothing to end: test the case with Run once.

Deputy14

Get a Location Details

Action

In Make“Provides details about the specified location.”

Reads everything Deputy knows about one location from its ID, handing you a single bundle of site details to reuse in the next modules.

When to use it

a trigger gives you only a location ID and your email or report needs the site's actual name and details.

Watch out

it needs an exact ID. If you only have a name, list your sites with List My Locations first.

Deputy15

Get a Location Settings

Action

In Make“Provides settings of a specific location.”

Returns the configuration of a specific location, which is what you check before changing it or copying it to another site.

When to use it

before running Update a Location Settings, read the current values so the scenario can compare them or keep a copy.

Watch out

this is the settings view, not the general profile. For the site's descriptive details, Get a Location Details is the better pick.

Deputy16

Get an Employee

Action

In Make“Provides details about the specified employee.”

Pulls the full profile of one employee, so a scenario that starts with a bare ID can still write a message that names the right person.

When to use it

a timesheet or leave trigger carries an employee ID, and the next step needs that person's name or contact details.

Watch out

it returns one person. To go through the whole team, List Employees is the module that sends out one bundle per employee.

Deputy17

Get a Schedule

Action

In Make“Provides details of a schedule.”

Fetches the full details of a single shift, filling in what a trigger or a stored ID leaves out before you notify anyone.

When to use it

a comment or update points to a schedule, and the message you send should state the shift's details clearly.

Watch out

when you need several shifts at once, reach for List Schedules instead of calling this module in a loop.

Deputy18

Get My Contact and Address

Action

In Make“Provides a user's contact and address.”

Returns a user's contact details and address as Deputy holds them, useful when a scenario must reach someone outside the app.

When to use it

a document or letter prepared elsewhere needs the address on file in Deputy.

Watch out

judging by its name, it reads the user behind the connection, not any employee you choose. Check the bundle with Run once before relying on it.

Deputy19

Get My Details

Action

In Make“Provides a user's details.”

Tells you who a Deputy user is, returning their details in one bundle, a quick way to confirm which account a scenario is talking to.

When to use it

you run several connections and want each scenario to log which Deputy user performed the actions.

Watch out

as its name suggests, it most likely describes the connected account. For another employee's profile, use Get an Employee.

Deputy20

Invite an Employee

Action

In Make“Invites an employee.”

Sends an existing Deputy employee their invitation, so a new hire can log in, see shifts and clock in from day one.

When to use it

right after Create an Employee in an onboarding scenario, or when a manager ticks a box in your HR tracker.

Watch out

the module invites an employee, so the person has to exist in Deputy first. Place it after Create an Employee, never before.

Deputy21

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Reaches any part of the Deputy API that the ready-made modules do not cover, using the connection you already set up, so you are not stuck when a module is missing.

When to use it

you need a Deputy object or action that has no module among the 53, and you are comfortable reading Deputy's API documentation.

Watch out

Make will not build the request for you. Test each call with Run once and read the returned bundle closely.

Deputy22

Pause / Unpause a Timesheet

Action

In Make“Pauses / unpauses a user's timesheet.”

Puts a user's running timesheet on hold, or resumes it, which is how a break can be recorded without the employee opening Deputy.

When to use it

a break button on a kiosk or a form triggers the pause, and a second press resumes the clock.

Watch out

the same module does both jobs. Map the choice carefully, or a resume can end up recorded as a new pause.

Deputy23

Publish a Schedule

Action

In Make“Publishes a schedule.”

Publishes a shift in Deputy so the rostered person can actually see it, the step between a planner's draft and a confirmed shift.

When to use it

after Create a Schedule, once a filter or an approval in another tool says the shift is final.

Watch out

staff see what you publish. Keep a check in front of this module rather than publishing every draft the moment it exists.

Deputy24

Start a Timesheet

Action

In Make“Starts a shift for your staff.”

Clocks a staff member in by starting their shift in Deputy, turning an event somewhere else into the start of recorded work time.

When to use it

a badge reader, a check-in form or a job start in a field app should open the Deputy timesheet without a second tap.

Watch out

pair it with End a Timesheet. A shift started automatically and never closed leaves you with hours to correct by hand.

Deputy25

Terminate an Employee

Action

In Make“Terminates an active employee.”

Ends an active employee's status in Deputy, the clean offboarding step that keeps former staff off future rosters while their records stay available.

When to use it

a leaving date is confirmed in your HR system and the person should no longer be scheduled.

Watch out

this is reversible with Activate a Terminated Employee, unlike Delete a Discarded Employee, which is why it should always come first.

Deputy26

Update a Location Settings

Action

In Make“Updates a location settings.”

Changes the settings of a Deputy location, letting a decision made elsewhere update the site's configuration without a manual edit.

When to use it

a site's details change in your source system and Deputy should reflect it for everyone working there.

Watch out

read the current values with Get a Location Settings first, so the scenario only changes what you meant and you keep a record of the old setup.

Deputy27

Update an Employee

Action

In Make“Updates an employee details.”

Edits an existing employee's details in Deputy, so your HR tool can stay the reference and Deputy follows it.

When to use it

a phone number, email or role changes in your HR software and the Deputy profile should match.

Watch out

each change fires Watch Employees Updates. Never pair the two in one scenario, or every update starts another run.

Deputy28

Update a Schedule

Action

In Make“Updates a Schedule.”

Modifies a shift already planned in Deputy, keeping the roster in step when the source of the booking moves.

When to use it

a client pushes a job back in your booking system and the Deputy shift should shift with it.

Watch out

the change can trigger Watch Schedules Updates. Keep that listener in a separate scenario.

Deputy29

Update or Create a Timesheet

Action

In Make“Updates a given timesheet or creates a new one.”

Fixes an existing timesheet, or writes a new one when none exists, so missing or wrong hours can be settled from another source.

When to use it

hours logged in a field app or a job tracker should become, or correct, the Deputy timesheet used for pay.

Watch out

the same module can update or create. Run once on test data to confirm you are updating the right entry, not adding a second one.

Deputy30

List Employees

In Make“Lists all employees.”

Returns your whole staff list, one bundle per employee, which lets you act on every person in a single scenario.

When to use it

you want to sync the full team to a spreadsheet or HR tool, or find someone by a detail other than their ID.

Watch out

every employee is a bundle, and every module after it runs once per bundle. Filter early to save operations.

Deputy31

List Location's News Feeds

In Make“Lists news feeds for a specific location.”

Gathers the announcements posted for a given location, giving you that site's news feed as bundles you can archive or repost.

When to use it

a regional manager wants each site's announcements collected in one document or channel.

Watch out

it covers a single location. To cover several sites, feed it location IDs from List My Locations.

Deputy32

List My Colleagues

In Make“Lists a user's colleagues.”

Lists the colleagues of a Deputy user, useful to find who works alongside someone before contacting the team.

When to use it

a shift is dropped at the last minute and the scenario should message the people who share that user's workplace.

Watch out

the result depends on the user behind the connection. For the whole company, List Employees is the safer choice.

Deputy33

List My Completed Tasks

In Make“Lists a user's completed tasks.”

Retrieves the tasks a user has already finished in Deputy, a simple way to show what got done on a shift.

When to use it

a handover report sent after a shift should include the checklist items marked done.

Watch out

open tasks are not in this list, only finished ones. A report built on it shows progress, not what is still missing.

Deputy34

List My Leave Requests

In Make“Lists a user's leave requests.”

Brings back a user's leave requests as bundles, so you can review their time off outside Deputy.

When to use it

a planning sheet should show every request of one user before a manager plans the coming period.

Watch out

for new requests as they arrive, Watch New Leave Requests is the better start. This module answers a question; it does not wait for events.

Deputy35

List My Locations

In Make“Lists a user's locations.”

Lists the locations a user belongs to, the quickest way to get the site IDs that many other Deputy modules ask for.

When to use it

before Get a Location Details, Create a Location or a news feed listing, to find the right site ID.

Watch out

you get one bundle per location, so later modules repeat for each site unless you pick one with a filter.

Deputy36

List My News Feeds

In Make“Lists a user's news feeds.”

Returns the announcements a user can see in their news feed, as bundles ready to copy, summarize or archive.

When to use it

staff who rarely open Deputy should get a digest of their feed in email or chat.

Watch out

this reads one user's feed. For a single site's announcements whoever reads them, List Location's News Feeds fits better.

Deputy37

List My Notifications

In Make“Lists a user's notifications.”

Collects a user's Deputy notifications, letting you surface alerts in a place that user checks more often than the app.

When to use it

a manager wants their Deputy alerts relayed to the tool where they spend their working day.

Watch out

each run returns the list as it stands, so the same notification can come back. Store what you already sent and filter it out.

Deputy38

List My Schedule Shifts

In Make“Lists a user's schedule shifts.”

Returns a user's planned shifts, one bundle each, so their roster can be copied to a calendar or shared outside Deputy.

When to use it

an employee wants their upcoming shifts in a personal calendar after each roster change.

Watch out

it covers the connected user's shifts. For the whole team's roster, List Schedules is the module to use.

Deputy39

List My Timesheets

In Make“Lists a user's timesheets.”

Gives back a user's timesheets as a list, the raw material for checking hours or building a personal summary.

When to use it

a contractor needs their recorded hours sent to an invoicing sheet when a job wraps up.

Watch out

to catch timesheets as they are saved, Watch New Timesheets reacts on its own; this module only answers when the scenario asks.

Deputy40

List My Unavailability Records

In Make“Lists a user's unavailability records.”

Lists the times a user has marked as unavailable, so planning tools outside Deputy know when not to book them.

When to use it

a dispatcher assigns jobs in another app and should see each person's blocked times first.

Watch out

unavailability is not leave. Combine it with List My Leave Requests if you need the full picture of who is away.

Deputy41

List Schedules

In Make“Lists all schedules (-12 hours to 36 hours from current date).”

Pulls every Deputy schedule around the current moment, from 12 hours back to 36 hours ahead, one bundle per schedule. You see at a glance who is due to work soon.

When to use it

a manager needs the whole team rather than one person, for example to post tomorrow's staffing in a shared channel. That is where it beats List My Schedule Shifts.

Watch out

the window is fixed, so a shift beyond 36 hours will not appear, and every bundle costs operations in the modules that follow.

Need help

Need help automating Deputy with Make?

A person reads every message.

FAQ

Deputy Make integration: frequently asked questions

01Is the Deputy Make integration free?

Yes, Deputy is a standard app in Make, so its modules are available from the Free plan. That plan has its own limits: 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits and count usage in credits each month. You still need your own active Deputy account, which is billed by Deputy, not by Make.

02What do you need to connect Deputy to Make?

You need an active Deputy account and OAuth credentials created in it. In Deputy, open the OAuth clients section, click New OAuth Client, name it, enter the callback URI given in the Make documentation and save. Copy the Client ID and the Client secret. In Make, add a Deputy module, click Create a connection, give it a name if you like and paste both values. With an instant trigger, click Create a webhook first, then create the connection.

03Do Deputy triggers in Make react in real time?

Yes. All 12 Deputy triggers are instant: Deputy calls Make through a webhook as soon as the event happens, whether it is a new employee, a leave request, a saved timesheet or a changed schedule. You do not set a polling interval on them, and a scenario only runs when Deputy has something to send. Each run still spends operations, one per module executed, so a busy trigger such as Watch New Comments is worth filtering right after it starts.

04What if a Deputy module is missing in Make?

Use Make an API Call. It is one of the 53 Deputy modules and reaches any endpoint of the Deputy API with the connection you already created, so an object or action without its own module is still within reach. You will need Deputy's API documentation to build the request. Also note that Make's documentation for Deputy is flagged as AI-generated from Deputy's docs, so check anything critical with Run once on a test account.

05Should you use Make or n8n for Deputy?

It depends on the tool your team already works in and what you need to automate. On the Make side, Deputy brings 53 modules: 12 instant triggers, 29 actions, 12 searches and Make an API Call for the rest, all on the Free plan. Many apps also have an n8n node, so check whether the Deputy node covers the events and actions your flow needs before choosing. Our comparison page, linked in the section above, sets out the differences between the two tools.

Add a Deputy module

Name the connection

Paste your Deputy credentials

Start a new scenario

Hook up the webhook

Add the onboarding task

Test with Run once

Switch it on

Need help automating Deputy with Make?