Connect Google Calendar to Apaleo

When something happens in Google Calendar, Notis takes the next step in Apaleo. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Google Calendar to Apaleo

View example

Check Property IDs in New Calendar Events

When a new calendar event is created, check whether its referenced Apaleo property exists and send a run report for anything that needs attention.

View example

Review Apaleo Property After Event Changes

When a calendar event changes, retrieve the referenced Apaleo property and report its current details alongside the event change for a quick review.

View example

Verify Property Before an Operations Event

Before a calendar event starts, check whether its referenced Apaleo property exists and report the result while there is still time to correct the reference.

View example

Check Apaleo Unit Count for Calendar Reviews

When full calendar event data syncs, check the matching Apaleo unit count and report it for planning or review, using a property filter supplied in the event or instruction.

View example

List Apaleo Unit Groups for Scheduled Reviews

Use a full calendar event sync to retrieve Apaleo unit groups for the property or criteria specified in the event or instruction, then include the list in the run report.

View example

Add Apaleo Unit Details to New Event Prep

When a new calendar event is created, retrieve the Apaleo units matching the criteria specified for the event and summarize them in the run report.

View example

Get a Scheduled Apaleo Property Count

On a recurring schedule, retrieve the total number of Apaleo properties and send the count in a run report for a lightweight portfolio check.

Supported Triggers and Actions

Notis builds workflows that link Google Calendar to Apaleo. A trigger fires from one place; an action lands in another.

Google Calendar triggers

Apaleo actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Archive a property

Use this endpoint to archive an existing live property this operation set the isarchived flag to true you must have at least one of these scopes: 'properties.manage, setup.manage'.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Check if a property exists

Check if a property exists by id. you need to be authorized (no particular scope required)

ActionInstant

Attendee Response Changed

Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.

TriggerPolling

Check if a unit attribute exists

Check if a unit attribute exists you must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.

ActionInstant

Event Canceled or Deleted

Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.

TriggerPolling

Check if a unit exists

Check if a unit exists by id. you must have at least one of these scopes: 'units.read, setup.read, setup.manage'.

ActionInstant

Event Starting Soon

Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.

TriggerPolling

Check if a unit group exists

Check if a unit group exists by id. you must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.

ActionInstant

Calendar Event Changes

**SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger).

TriggerInstant

Clones a property

Use this call to clone a specific property. this operation creates a new property with inventory and rate plans from the specified property. you must have at least one of these scopes: 'properties.create, setup.manage'.

ActionInstant

Event Created

Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.

TriggerPolling

Create a unit

Use this call to create a new unit. you must have at least one of these scopes: 'units.create, setup.manage'.

ActionInstant

Calendar Event Sync

Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).

TriggerPolling

Create a unit attribute

Use this call to create a new unit attribute. you must have at least one of these scopes: 'unitattributes.create, setup.manage'.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.