Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Deputy
Google Calendar

Connect Deputy and Google Calendar

Explore ready-made Deputy and Google Calendar templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Deputy with Google Calendar and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Deputy
Trigger: Watch Employees Deletion
Google Calendar
Action: Select an action
1. Select a trigger

  • Triggers when an employee has been deleted.

  • Triggers when an employee has been updated.

  • Triggers when a new area or department has been created.

  • Triggers when a comment has been added.

  • Triggers when a new employee has been created.

  • Triggers when a new leave request has been submitted.

  • Triggers when a new schedule has been added.

  • Triggers when a new timesheet has been saved.

  • Triggers when an announcement has been deleted.

  • Triggers when a schedule has been deleted.

  • Triggers when a schedule has been updated.

  • Triggers when a timesheet has been updated.

2. Select an action

  • Clears a primary calendar. This operation deletes all events associated with the primary calendar of an account.

  • Creates a new calendar.

  • Creates a new access control rule.

  • Creates a new event.

  • Deletes a calendar.

  • Deletes an access control rule.

  • Deletes an event.

  • Duplicates an event.

  • Returns metadata for a calendar.

  • Returns metadata of an access control rule.

  • Returns metadata for an event in the specific calendar.

  • Returns free/busy information for a set of calendars.

  • Performs an arbitrary authorized API call.

  • Updates an existing calendar.

  • Updates an existing access control rule.

  • Updates an existing event.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Deputy and Google Calendar.

Activate a Terminated Employee
Activates a terminated employee.
Action
Approve a Timesheet
Approves a timesheet.
Action
Clear a Calendar
Clears a primary calendar. This operation deletes all events associated with the primary calendar of an account.
Action
Create / Update a Journal
Creates or updates a journal.
Action
Create a Calendar
Creates a new calendar.
Action
Create a Location
Creates a new location (workplace / company).
Action
Create a News Feed
Creates a news feed announcement.
Action
Create a Schedule
Creates a new schedule / roster.
Action
Create a Task
Creates a new task.
Action
Load more

Popular Deputy and Google Calendar workflows

Connect Deputy and Google Calendar with Make. Automate manual tasks, sync real-time data, and build more efficient workflows.

App Families

Add your Deputy schedule to Google Calendar

Every time a new schedule is created for you in Deputy, Make automatically will create a new detailed event in Google Calendar.

Add your Deputy schedule to Google Calendar
Use template

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.