Skip to main content

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

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

Connect BeLazy and Google Calendar

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

Get started free

Create a custom workflow

Integrate BeLazy 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.

BeLazy
Trigger: Watch New Approved Project
Google Calendar
Action: Select an action
1. Select a trigger

  • Triggers when BeLazy notifies Make of new incoming project that is approved automatically or manually. The module returns with an iteration through the available projects in BeLazy.

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 BeLazy and Google Calendar.

Accept An Opportunity
Accepts an opportunity, which creates a project in BeLazy and begins transferring it to your BMS. Please note, that acceptance is an instantaneous process, however, project creation and transferring it to the BMS is an asynchronous process. This operation is applicable when you want to control what opportunities to accept or dismiss.
Action
Acknowledges Project
Acknowledges the successful processing of a project received from BeLazy. Projects not acknowledged will remain in the active project list.
Action
Add File To Workspace
Adds a file to a workspace. The file must already be uploaded; with this operation the file is added to the the workspace and its properties are set. If a file is already added to the workspace the properties of the file are set.
Action
Add/Update Deliverable
Adds a new deliverable file to a project or updates the properties of an existing deliverable file. Adding the deliverable registers the deliverable file (but does not start the delivery process). This operation is applicable when your system is acting as a BMS and wants to deliver projects into BeLazy.
Action
Clear a Calendar
Clears a primary calendar. This operation deletes all events associated with the primary calendar of an account.
Action
Clear Vendor Of Project
Clears the vendor assigned to the project's pricing item in the BMS. As a result, BeLazy will try to remove this assignments in the origin system. This operation is applicable when using a REST Api BMS and project creation in the BMS has been acknowledged.
Action
Create a Calendar
Creates a new calendar.
Action
Create an Access Control Rule
Creates a new access control rule.
Action
Create an Event
Creates a new event.
Action
Load more

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.