Connect Google Docs to DeployHQ
When something happens in Google Docs, Notis takes the next step in DeployHQ. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Google Docs to DeployHQ
Create a DeployHQ project for every new Google Doc
Turn each newly created Google Doc into a ready DeployHQ project record.
Deploy configuration when a Google Doc placeholder is filled
Use a completed document template to trigger a DeployHQ configuration file deployment.
Summarize deployment impact from matching document updates
Analyze updated Google Docs that match a query and generate a DeployHQ revision overview.
Review deployment history after a Google Doc update
When a tracked document changes, retrieve the related DeployHQ deployment history for review.
Refresh config inventory after document structure changes
When a Google Doc structure changes, retrieve the DeployHQ config file inventory for verification.
Check deployment targets when a document reaches a size threshold
When a Google Doc crosses a word or character threshold, retrieve its DeployHQ server groups.
Check the latest repository revision when a release keyword appears
Detect a release keyword in Google Docs and retrieve the latest DeployHQ repository revision.
Attach recent commits and tags to every new release document
When a new Google Doc is added, retrieve recent commits and tags from the relevant DeployHQ branch.
Review the DeployHQ project when a source document is deleted
When a Google Doc is trashed, retrieve the associated DeployHQ project for a cleanup decision.
Supported Triggers and Actions
Notis builds workflows that link Google Docs to DeployHQ. A trigger fires from one place; an action lands in another.
Google Docs 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.
New Document Created
Triggers when a new Google Doc is created. This trigger monitors Google Docs and fires when new documents are detected. Uses timestamp filtering to efficiently poll for new documents.
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.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
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.
Document Placeholder Filled
Triggers when a Google Doc's plain text changes such that a configured placeholder token/pattern is no longer present (i.e., the document has been filled in). This trigger monitors a specific Google Doc and fires when a placeholder pattern that was previously present is no longer found in the document's plain text.
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.
Document Search Update
Triggers when a Google Doc matching a user-defined search query is newly created or updated since the last poll. This trigger uses timestamp filtering to efficiently monitor documents.
Delete Template
Tool to delete a template by its unique permalink. Use when you need to permanently remove a template from DeployHQ.
Document Structure Changed
Triggers when a Google Doc's structure changes (headers/footers added/removed, tables/images count changes). This trigger monitors a specific document for structural changes like: - Headers added or removed - Footers added or removed - Tables added or removed - Images (inline objects) added or removed - Positioned objects added or removed - Footnotes added or removed
Get Projects
Tool to retrieve all projects from DeployHQ account. Use when you need to list all available projects and their configurations.
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
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.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Google Docs and DeployHQ
Connect any two apps with Notis in the middle.
Google Docs 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.