Connect Google Calendar to Chaser
When something happens in Google Calendar, 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 Calendar to Chaser
Flag invoice follow-up when an attendee declines
When an event attendee declines, ask Notis to find the related Chaser invoice and update its status for follow-up.
Review customer contact details after an RSVP decline
Use a declined RSVP as a cue to review the related Chaser customer contact details and update them when you provide the correction.
Review invoice dates when a calendar event is canceled
When an event is canceled, have Notis find any associated Chaser invoice and review whether its due date or status needs updating.
Check invoice status before an event starts
Before a scheduled event starts, have Notis check the related Chaser invoice and apply a status update only when your rule and invoice match are clear.
Confirm customer contact details before an event
As an event approaches, ask Notis to check the associated Chaser customer record and apply a contact update you confirm.
Create a Chaser customer for a new calendar relationship
When a new event introduces a customer who is not yet in Chaser, have Notis create a customer using the details and credentials you provide.
Review Chaser customer records for a new event
When a new event is created, have Notis check the Chaser customer list to verify whether the intended customer record exists.
Look up Chaser customer details from calendar context
Use full Google Calendar event data to identify a customer and retrieve their Chaser record by the external ID you supply or establish.
Audit Chaser customer coverage against calendar events
Use full calendar event data to identify customer relationships and search Chaser's customer list for records needing review.
Supported Triggers and Actions
Notis builds workflows that link Google Calendar to Chaser. A trigger fires from one place; an action lands in another.
Google Calendar 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.
Attendee Response Changed
Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.
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.
Event Canceled or Deleted
Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.
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.
Event Starting Soon
Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.
Get Organization
Tool to retrieve information about the connected organizations. use when you need organization ids, currency, timezone, or legal details before other operations.
Calendar Event Changes
**SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger).
Create Credit Note
Tool to create a new credit note record in the organization. use after confirming invoice adjustments.
Event Created
Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.
Create Customer
Tool to create a new customer record in chaser. use after obtaining basic auth credentials.
Calendar Event Sync
Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).
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 Calendar and Chaser
Connect any two apps with Notis in the middle.
Google Calendar 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.