Connect Google Docs to Demio
When something happens in Google Docs, Notis takes the next step in Demio. 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 Demio
Discover Demio events when a new Google Doc is created
When a new planning document appears, retrieve available Demio events so you can choose the right webinar without leaving your workflow.
Check a Demio event when a document placeholder is filled
When the event ID placeholder in a Google Doc is completed, retrieve the Demio event details and summarize the session metadata.
Show Demio session dates for updated webinar documents
When documents matching your webinar search are created or updated, retrieve the scheduled Demio dates and summarize timing changes.
Refresh Demio metadata after a Google Doc update
When an existing document changes, retrieve the referenced Demio event and report the current title, status, and available metadata.
Review Demio participants when a webinar brief reaches its word threshold
When a planning document reaches a chosen size, list Demio participants and summarize registration progress for a launch review.
Create a Demio join link when a keyword appears in a Google Doc
When a configured keyword such as approved appears in a document, register the intended attendee and return a unique Demio join link.
Check Demio sessions after a webinar document structure change
When tables, headers, footers, or images change in a monitored document, list the referenced Demio session dates for a structural review.
List Demio events for every new campaign document
When a new campaign document is added, retrieve Demio events and summarize which existing sessions could support the campaign.
Retrieve Demio details when a webinar document is deleted
When a monitored document is trashed, retrieve its referenced Demio event details so the team can assess what still needs attention.
Supported Triggers and Actions
Notis builds workflows that link Google Docs to Demio. A trigger fires from one place; an action lands in another.
Google Docs triggers
Demio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Demio Create Join Link
Tool to register an attendee and obtain their unique Demio join link. Use after confirming a valid event_id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Demio: Get Event by ID
Tool to retrieve event details by ID. Use when you need the full metadata for a specific Demio event.
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.
List Event Date Participants
Tool to list participants for a specific event date. Use after scheduling an event session to retrieve attendees.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
List Event Dates
Tool to list all scheduled session dates for a given Demio event. Use when you need the session schedule by event ID.
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.
List Demio Events
Tool to retrieve a list of Demio events. Use when you need to fetch events optionally filtered by type or paginated.
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.
Demio API Ping
Tool to perform a health check on the Demio API. Use to verify the API is reachable before other calls.
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
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
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 Demio
Connect any two apps with Notis in the middle.
Google Docs and Demio, 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 Demio.