Bring deployment history to a shared plan
When a deployment plan reaches new collaborators, the recent release history can provide useful context. Notis can retrieve the project history and report the results alongside the sharing event.
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
Get Project Deployments
Tool to retrieve a paginated list of all deployments in a project. Use when you need to view deployment history for a specific project. Results are paginated with 10 deployments per page.
Why this helps
A newly shared plan often arrives without the deployment context a collaborator needs to get up to speed.
- Bring recent deployment context into the handoff
- Reduce manual history lookups
- Give collaborators a useful report with the share event
Setup
Build it in a few focused steps.
- 1Connect Google Drive and DeployHQ once in the Notis portal.
- 2Create an automation in Automations, New Automation, and add its name and prompt.
- 3In one instruction, ask Notis to identify the related DeployHQ project from the shared plan and retrieve its deployment history for the run report.
- 4Choose the Google Drive File Shared trigger and select where run reports should go.
- 5Test with one real deployment plan share.
Questions about this workflow
Does sharing a Drive file trigger a deployment?
No. This workflow retrieves the DeployHQ deployment history for context and reports it; it does not start a deployment.
What if the plan does not identify a DeployHQ project?
Include the project identity in the plan. If it cannot be identified from the available information, the run should report that limitation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to DeployHQ. A trigger fires from one place; an action lands in another.
Google Drive triggers
DeployHQ actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Command
Tool to delete a command from a specified project. Use when you need to remove an SSH command from a project's configuration.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Project
Tool to delete a project from DeployHQ. Use when you need to permanently remove a project by its permalink or identifier.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Delete Build Cache File
Tool to delete an existing build cache file from a project. Use when you need to remove a cached build artifact from the project's build cache storage.
File Created
Triggers when a new file is created in Google Drive.
Delete Excluded File Rule
Tool to delete an existing excluded file rule from a project. Use when you need to remove an excluded file pattern from deployment configuration.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Delete Server Group
Tool to delete a server group from a project using the DeployHQ API. Use when you need to remove a server group from deployment configuration.
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.
Delete Template
Tool to delete a template by its unique permalink. Use when you need to permanently remove a template from DeployHQ.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Get Projects
Tool to retrieve all projects from DeployHQ account. Use when you need to list all available projects and their configurations.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Get Project
Tool to view an existing project in DeployHQ. Use when you need to retrieve details about a specific project by its permalink or identifier.
Connect any two apps with Notis in the middle.
Google Drive and DeployHQ, 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 DeployHQ.