Connect Gmail to Demio

When something happens in Gmail, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Gmail to Demio

View example

Send Demio join links after invitation emails

After you send a webinar invitation, find the matching Demio event and session, then register the recipient and provide their unique join link for follow-up.

View example

Answer webinar date questions with Demio schedules

When a new Gmail message asks about a webinar schedule, look up the matching Demio event's scheduled dates so you can reply with accurate session options.

View example

Identify the webinar behind an incoming question

When a Gmail message asks about an event without naming it clearly, retrieve the Demio event list to help identify the likely webinar and prepare a focused follow-up.

View example

Check event details before answering attendee questions

Use an incoming Gmail question to identify a specific Demio event and retrieve its metadata before preparing a response about that webinar.

View example

Register webinar attendees from Gmail requests

When an incoming email clearly requests a webinar registration, identify the Demio event, confirm it is valid, then create the attendee registration and retrieve a unique join link.

View example

Check Demio attendance details for email follow-up

When an attendee asks about a specific session, identify the event date and retrieve its participant list so you can review the relevant attendance details before responding.

View example

Check Demio availability after webinar coordination

After sending a coordination email about a webinar, run a Demio API health check and include its result in the run report so you can spot access issues early.

Supported Triggers and Actions

Notis builds workflows that link Gmail to Demio. A trigger fires from one place; an action lands in another.

Gmail triggers

Demio actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Demio Create Join Link

Tool to register an attendee and obtain their unique Demio join link. Use after confirming a valid event_id.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Demio: Get Event by ID

Tool to retrieve event details by ID. Use when you need the full metadata for a specific Demio event.

ActionInstant

Email Sent

Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.

TriggerPolling

List Event Date Participants

Tool to list participants for a specific event date. Use after scheduling an event session to retrieve attendees.

ActionInstant

New Gmail Message Received Trigger

Triggers when a new message is received in Gmail.

TriggerPolling

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.

ActionInstant

List Demio Events

Tool to retrieve a list of Demio events. Use when you need to fetch events optionally filtered by type or paginated.

ActionInstant

Demio API Ping

Tool to perform a health check on the Demio API. Use to verify the API is reachable before other calls.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.