Connect Google Calendar to Elorus

When something happens in Google Calendar, Notis takes the next step in Elorus. 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 Google Calendar to Elorus

View example

Invoice a completed client session

Create an Elorus invoice after a client session ends, using the billing rules and rates you provide.

View example

Check accepted attendees against Elorus contacts

When an attendee accepts a calendar invitation, look up Elorus contacts to help confirm the billing identity before work begins.

View example

Review the client contact before a call

Before a calendar event starts, look up likely Elorus contacts so billing details are easy to find after the call.

View example

Prepare billing after a client event changes

When an existing calendar event changes, assess the updated details against your billing rules and prepare an invoice only when appropriate.

View example

Review invoices when a client event is canceled

When a calendar event is canceled, search Elorus invoices for relevant records and report any that may need your review.

View example

Check client invoices before a meeting

When the calendar sync returns full event details, look up relevant Elorus invoices so you can prepare for a client conversation.

View example

Prepare for a billing call with invoice records

As a billing call approaches, retrieve relevant Elorus invoices and summarize the available details for your prep.

View example

Email an approved Elorus invoice

Start a webhook workflow with an approved invoice and contact reference, then email the existing invoice through Elorus.

View example

Review Elorus invoices on a schedule

Run a recurring invoice search using filters you supply and receive a concise review of records that may need follow-up.

Supported Triggers and Actions

Notis builds workflows that link Google Calendar to Elorus. A trigger fires from one place; an action lands in another.

Google Calendar triggers

Elorus actions

Recurring trigger

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

TriggerScheduled

Create Invoice

Create an invoice or receipt, saved as a draft by default.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Expense

ActionInstant

Attendee Response Changed

Trigger when an attendee accepts, declines, or tentatively responds to an invitation.

TriggerPolling

CREATE_PRODUCT

Create a product or service in the catalog.

ActionInstant

Event Canceled or Deleted

Trigger when a calendar event is canceled or deleted.

TriggerPolling

Email Invoice

Email an existing invoice to selected contacts.

ActionInstant

Event Starting Soon

Trigger when a calendar event is within the configured time before it starts.

TriggerPolling

Get Bills

Retrieve bills for viewing and managing expenses or purchases.

ActionInstant

Calendar Event Changes

Trigger in real time when a calendar event changes.

TriggerInstant

Delete Invoice

ActionInstant

Event Created

Trigger when a new calendar event is created.

TriggerPolling

Get Contacts

Retrieve your contacts.

ActionInstant

Calendar Event Sync

Retrieve full calendar event details through polling.

TriggerPolling

Get Credit Notes

Retrieve credit notes.

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.