Turn a scheduling request into a validated intro call
Send one request with the contact details and proposed time. Notis checks the email, then adds the call to Google Calendar when the request is complete.
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
Scheduling requests can turn into extra back and forth when contact details are invalid or the proposed time gets lost.
- Catch invalid email addresses before adding a call.
- Keep contact details and the proposed time together in the request.
- Reduce manual calendar entry.
Setup
Build it in a few focused steps.
- 1Connect Abstract and Google Calendar once in the Notis portal.
- 2Create an automation from Automations, New Automation, or tell Notis what you want from any channel.
- 3In one instruction, ask Notis to validate the submitted email with Abstract and create an intro call from the supplied title and RFC3339 UTC start and end times when validation succeeds.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real scheduling request that includes a valid email and times.
Questions about this workflow
What starts this automation?
An HTTP request to its Notis webhook starts it. Include the contact email and the proposed event details in the request.
Does this workflow check calendar availability?
No. It validates the email and creates the event from the supplied time. Use a separate availability check before confirming a time.
What time format should the request include?
Provide RFC3339 UTC start and end times, with the end after the start.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abstract to Google Calendar. A trigger fires from one place; an action lands in another.
Abstract 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.
Abstract 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.