Review Related Appointo Bookings After Drive Sharing Changes
A shared file can signal that appointment details are ready for review. Find related bookings and get a focused summary for the next step.
Trigger
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Action
List Bookings
Tool to list bookings. Use when you need to fetch bookings filtered by status, paging, or search term.
Why this helps
A newly shared file may need booking follow-up, but the connection between the document and an Appointo booking is easy to lose.
- Prompt a booking search when sharing changes.
- Keep the follow-up tied to the shared file context.
- Avoid changing booking records without an explicit request.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Appointo once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for shared-file booking review.
- 3Tell Notis to use the shared file's available context to search Appointo bookings and report plausible matches, stating when a match is uncertain.
- 4Choose the Google Drive File Shared trigger and select a report channel.
- 5Test with one real sharing event and review the matches in the report.
Questions about this workflow
Does sharing a file expose booking details to the new recipient?
This workflow searches and reports through your chosen Notis report channel. Use a channel appropriate for the information and tell Notis to include only necessary details.
Will it share or modify a booking?
No. The action lists bookings for review and does not alter Appointo records.
What if the shared file has no useful booking reference?
Notis should report that it could not identify a likely booking rather than infer one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Appointo. A trigger fires from one place; an action lands in another.
Google Drive triggers
Appointo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authenticate Appointo API Token
Tool to authenticate with the Appointo API by validating the APPOINTO-TOKEN header. Use when verifying the token before subsequent API calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cancel Booking
Tool to cancel a booking or selected customers. Use when you need to revoke an entire booking or individual attendees after verifying booking details. Use after retrieving booking information.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Booking
Tool to create a new booking. Use when scheduling a customer booking after confirming appointment availability.
File Created
Triggers when a new file is created in Google Drive.
Get Appointment Availability
Tool to get calendar availability for a specific appointment. Use when you need to fetch available time slots for an appointment within a date range.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
List Appointments
Tool to list appointments. Use when fetching appointments with optional filters and pagination after confirming a valid API token.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
List Bookings
Tool to list bookings. Use when you need to fetch bookings filtered by status, paging, or search term.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
List Products
Tool to fetch all available products. Use when browsing products with optional paging and search. Call after authenticating with Appointo API.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
List Subscription Contracts
Tool to list subscription contracts. Use when retrieving contracts with optional search after confirming a valid API token.
Connect any two apps with Notis in the middle.
Google Drive and Appointo, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Appointo.