Add a consistent service timestamp to Drive change reviews
Use Ably's service clock when a Drive change prompts a time sensitive review.
Trigger
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Action
Get Ably Service Time
This tool retrieves the current server time from ably's service in milliseconds since the epoch. it is particularly useful for time synchronization and generating valid tokenrequest timestamps to prevent replay attacks. the endpoint supports multiple content types, handles http errors, network issues, and is a fundamental tool for ensuring accurate timing in ably applications.
Why this helps
Review notes can be harder to reconcile when timestamps come from different clocks or are missing.
- Use the target service clock for a review timestamp
- Make change reviews easier to reconcile
- Avoid manually checking the current time
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Ably once in the Notis portal.
- 2Create an automation in Automations, or tell Notis the outcome in plain language.
- 3In one instruction, ask Notis to retrieve Ably service time when a Drive change occurs and include the timestamp in the run report.
- 4Choose the Google Drive Changes trigger and select where run reports should go.
- 5Test with one real change and confirm the returned time is presented clearly.
Questions about this workflow
What format does the action return?
It retrieves the current Ably server time in milliseconds since the epoch.
Does this verify when the Drive change happened?
No. It gives the current Ably service time when the automation runs, which can support a review timestamp.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Ably. A trigger fires from one place; an action lands in another.
Google Drive triggers
Ably actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Query Batch Presence
This tool enables querying the presence states of multiple channels in a single api request. the api retrieves the member presence details of the specified channels in parallel.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Batch Presence History
This tool enables querying presence history for multiple channels in a single api request. it uses the get endpoint at https://rest.ably.io/presence to retrieve the member presence history details of the specified channels in parallel.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Ably Channel
Creates a new channel or retrieves an existing channel in ably. this tool allows you to programmatically create and initialize channels for real-time messaging. since ably creates channels implicitly when first used, this action publishes an empty initialization message to create/activate the channel.
File Created
Triggers when a new file is created in Google Drive.
Delete Channel Subscription
This tool allows you to unsubscribe devices or clients from push notifications for specific channels. the operation is asynchronous, so immediate requests after deletion may briefly still return the subscription.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Get Channel Details
This tool retrieves metadata and details for a specific channel in ably. it returns a channeldetails object containing information about the channel's status, occupancy, and other metadata. the endpoint provides visibility into channel activity, including metrics such as connections, presence, publishers, and subscribers, and requires appropriate permissions.
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.
Get Channel History
This tool retrieves the message history for a specified ably channel. it uses the get /channels/{channelid}/messages endpoint to return a paginated list of messages in chronological order, subject to parameters such as 'channelid', 'limit', 'direction', 'start', and 'end'. the tool is useful for auditing, recovering missed messages, analyzing channel activity, and debugging message flows. authentication is required via basic or token authentication.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Get Channel Presence History
This tool retrieves the history of presence messages for a specified channel in ably. it allows you to query presence events on a channel within a given time period.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Get Ably Service Time
This tool retrieves the current server time from ably's service in milliseconds since the epoch. it is particularly useful for time synchronization and generating valid tokenrequest timestamps to prevent replay attacks. the endpoint supports multiple content types, handles http errors, network issues, and is a fundamental tool for ensuring accurate timing in ably applications.
Connect any two apps with Notis in the middle.
Google Drive and Ably, 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 Ably.