Connect Google Calendar to Detrack

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

View example

Turn New Pickup Appointments Into Detrack Collections

Create a Detrack collection when a new Google Calendar event schedules a pickup and includes the required collection details.

View example

Check Detrack Jobs Against Calendar Events

When a full calendar sync returns event details, have Notis check Detrack jobs for related work and report what it finds.

View example

Apply Calendar Changes to a Known Detrack Delivery

When an event changes, ask Notis to update a Detrack delivery only when the event identifies the delivery and the new details are clear.

View example

Check Detrack Jobs When an Attendee Responds

When an attendee changes their RSVP, have Notis check related Detrack jobs using references supplied in your event process.

View example

Search Detrack When a Calendar Event Is Near

Before an event starts, search Detrack using the job reference provided in the event process and report matching records.

View example

Review Detrack Jobs After a Calendar Cancellation

When a calendar event is canceled, have Notis list potentially related jobs for review using a supplied reference.

View example

Review Today's Detrack Deliveries Before Calendar Appointments

On a recurring schedule, retrieve deliveries for a chosen date and have Notis compare them with calendar events available to its instruction.

View example

Review the Detrack Fleet Before Scheduled Work

On a schedule, retrieve the Detrack vehicle list and prepare a fleet overview alongside the calendar context you specify.

View example

Look Up Detrack Jobs From an Incoming Request

Start from an HTTP request and search Detrack using criteria included in the request or your instruction.

Supported Triggers and Actions

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

Google Calendar triggers

Detrack actions

Recurring trigger

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

TriggerScheduled

Add Collection

Tool to add a new collection in detrack. use after gathering all necessary collection details.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete All Collections

Tool to delete all collections in the account. use when you need to purge every collection for a specific date after confirmation.

ActionInstant

Attendee Response Changed

Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.

TriggerPolling

Delete All Deliveries

Tool to delete all deliveries for a specific date. use when you need to purge deliveries in bulk before scheduling new ones.

ActionInstant

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.

TriggerPolling

Delete Delivery

Tool to delete one or more deliveries by date and d.o. number. use after confirming delivery entries to avoid accidental data loss (max 100 items per call).

ActionInstant

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.

TriggerPolling

Edit Delivery

Tool to edit specific deliveries by date and d.o. number. use after confirming delivery identifiers to update their details (max 100 per call).

ActionInstant

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).

TriggerInstant

List Jobs

Tool to list all jobs with optional filters and pagination. use when you need to retrieve jobs by date, status, country, or other criteria.

ActionInstant

Event Created

Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.

TriggerPolling

Search

Tool to search for deliveries, collections, or vehicles. use after defining search criteria to retrieve matching jobs.

ActionInstant

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).

TriggerPolling

View All Collections

Tool to view all collection jobs in detrack. use when you need to retrieve every collection job currently stored.

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.