Skip to content
Notis

Make room to respond when a sensor needs attention

When a device sends an alert, give the investigation a place on your calendar before it slips down the list.

Trigger

Webhook received

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

Action

Create Event

Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.

Why this helps

Device alerts can arrive while you are in the middle of other work, then disappear into a busy inbox before you investigate.

  • Reserve focused time to investigate important device alerts.
  • Keep an alert from becoming an easy-to-forget follow-up.
  • Use the incoming payload to summarize the reason for the block when available.

Setup

Build it in a few focused steps.

  • 1Connect Adafruit IO and Google Calendar once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3Tell Notis to create a response block when the webhook payload reports a sensor condition that needs investigation.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real Adafruit IO alert and check the calendar event.

Questions about this workflow

Does Adafruit IO provide the trigger for this workflow?

No Adafruit IO trigger event is listed here. Start the automation with a Notis webhook and send it an HTTP request when your alert process detects a condition worth investigating.

What event time will be scheduled?

Tell Notis how to choose a suitable time and block length. If the webhook payload does not include usable timing details, provide those rules in the instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Adafruit IO triggers

Google Calendar actions

Recurring trigger

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

TriggerScheduled

Insert Calendar into List

Inserts an existing calendar into the user's calendar list.

ActionInstant

Webhook trigger

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

TriggerInstant

Update Calendar List Entry

Updates an existing entry on the user\'s calendar list.

ActionInstant

Delete Calendar

Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.

ActionInstant

Update Calendar

Updates metadata for a calendar.

ActionInstant

Clear Calendar

Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.

ActionInstant

Create Event

Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.

ActionInstant

Delete event

Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.

ActionInstant

Create a calendar

Creates a new, empty google calendar with the specified title (summary).

ActionInstant

Connect any two apps with Notis in the middle.

Adafruit IO and Google Calendar, 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 Google Calendar.