Put Callingly lead follow-ups on your calendar
Send a follow-up request from Callingly and let Notis create a calendar event, so the next conversation has a time and a place.
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
Promising to follow up is easy; remembering to find time and carry the lead context into your calendar is where it slips.
- Keeps a lead follow-up on your calendar instead of in a separate note.
- Can include lead details and call context supplied in the webhook request.
- Reduces the chance that a promising conversation gets no next step.
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 create a Google Calendar event for each Callingly follow-up request, using the provided lead details and schedule.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real follow-up request that includes an event title, start time, end time, and any useful lead context.
Questions about this workflow
How does this automation start?
A webhook starts it when a request reaches Notis. Include the follow-up details and event times in the request.
Does Callingly provide the calendar time automatically?
The supplied Callingly description does not specify a trigger event or a time field. Include the desired start and end times in the webhook request.
What does Google Calendar need to create the event?
The event needs RFC3339 UTC start and end times, with the end after the start, and the connected user needs write access to the calendar.
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.