Connect Google Docs to Chaser
When something happens in Google Docs, Notis takes the next step in Chaser. 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 Chaser
Turn a new Google Doc into a Chaser invoice
Create a Chaser invoice when a new Google Doc contains complete billing details.
Update a Chaser invoice when a document is filled
Use a completed Google Doc template to update an existing Chaser invoice.
Review Chaser customers from matching documents
Search updated Google Docs for a client signal and retrieve the related Chaser customers.
Update a Chaser customer from an edited document
Apply confirmed contact changes from an updated Google Doc to the matching Chaser customer.
Create a Chaser customer when a document flags a new account
Create a Chaser customer when a new account keyword appears in a Google Doc.
Create an invoice when a billing brief reaches completion
Create a Chaser invoice when a Google Doc crosses your configured word threshold.
Create a Chaser credit note after a document structure change
Use a changed adjustment table or section as the signal to create a Chaser credit note.
Update a Chaser invoice when its source document is deleted
When a source Google Doc is trashed, update the related Chaser invoice for review.
Check Chaser organization details for each new work folder
Retrieve Chaser organization information when a new root Google Drive folder is created.
Supported Triggers and Actions
Notis builds workflows that link Google Docs to Chaser. A trigger fires from one place; an action lands in another.
Google Docs triggers
Chaser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Invoice
Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Credit Notes
Tool to retrieve a list of credit notes. use after authenticating this detail.
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.
Get Customer by ID
Tool to retrieve details for a specific customer by their external (source system) id. use after obtaining the external id when you need specific customer information.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
Get Customers
Tool to retrieve a list of all customers associated with the organization. use when you need to display or process complete customer contact and status information.
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.
Get Organization
Tool to retrieve information about the connected organizations. use when you need organization ids, currency, timezone, or legal details before other operations.
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.
Create Credit Note
Tool to create a new credit note record in the organization. use after confirming invoice adjustments.
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
Create Customer
Tool to create a new customer record in chaser. use after obtaining basic auth credentials.
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
Update Customer
Tool to update an existing customer's information using their unique externalid. use after confirming the customer's externalid. e.g., "update contactemailaddress for externalid cust abc123."
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 Chaser
Connect any two apps with Notis in the middle.
Google Docs and Chaser, 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 Chaser.