Share Your Availability Programmatically
External systems can query your available calendar time via webhook, enabling seamless scheduling without manual back-and-forth.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Find free slots
Finds free/busy time slots in google calendars for specified calendars within a defined time range (defaults to the current day utc if `time min`/`time max` are omitted), enhancing busy intervals with event details; `time min` must precede `time max` if both are provided.
Why this helps
Distributed teams and custom systems often can't access founder availability in real time, leading to scheduling delays and manual coordination.
- Enable external systems to check your availability automatically
- Eliminate scheduling back-and-forth with real-time availability data
- Support custom tools and workflows with availability APIs
- Streamline meeting booking with immediate availability responses
Setup
Build it in a few focused steps.
- 1Connect Google Calendar in Notis Integrations.
- 2Create an automation: 'When a webhook request asks for my availability, return free time slots for the requested date range.'
- 3Set the trigger to 'Notis Webhook' and share your webhook URL with external systems.
- 4Configure external systems to send GET/POST requests with date range parameters.
- 5Test by sending a webhook and verify you receive available time slots.
Questions about this workflow
What parameters should webhook requests include?
Minimum: start and end dates. Optional: specific calendars to check, minimum block size, or timezone. Document your expectations in the automation.
Can I restrict availability to specific time windows?
Yes. Specify business hours, meeting-free times, or other constraints in your automation prompt.
Is this secure for external systems?
Your webhook URL acts as an API key. Only share it with trusted systems. Consider rate limiting or authentication tokens.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Google Calendar. A trigger fires from one place; an action lands in another.
Jira triggers
Google Calendar actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
New Project
Triggered when a new project is added in Jira
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
Update Calendar
Updates metadata for a calendar.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
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.
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.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Not just Jira and Google Calendar. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Google Calendar.