Find open callback windows before setting follow-up times
Have Notis check free slots against your Callingly follow-up list, then use the report to choose a time that fits.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Choosing callback times from memory can create conflicts and turns a short follow-up into calendar juggling.
- Shows available windows for follow-ups that have not yet been scheduled.
- Uses calendar availability to reduce avoidable conflicts.
- Puts the callback list and possible windows in one report.
Setup
Build it in a few focused steps.
- 1Connect Callingly and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to review the Callingly follow-ups you provide and report suitable free Google Calendar slots within the requested time range.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with one real follow-up list and a time range that includes a known open and busy period.
Questions about this workflow
Does this book callbacks automatically?
No. It finds free slots and reports them so you can choose a time. It does not create an event.
What information must I provide?
Provide the Callingly follow-ups to plan and a defined time range. The free slots action requires the start of the range to precede the end.
Will the report include event details?
The free slots action can enhance busy intervals with event details. The available details depend on what Google Calendar returns for the connected calendars.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Callingly to Google Calendar. A trigger fires from one place; an action lands in another.
Callingly triggers
Google Calendar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
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.
Callingly 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.