Put Ashby interviews on your calendar without retyping the details
Send an Ashby interview request to Notis and have the meeting appear in Google Calendar with the relevant recruiting context.
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
Interview details live in the hiring pipeline, while calendar setup requires re-entering them and can lead to missed or inconsistent information.
- Reduce duplicate entry between recruiting and calendar tools.
- Keep the candidate, role, and interview purpose visible in one event.
- Spend less time switching between Ashby and Google Calendar.
Setup
Build it in a few focused steps.
- 1Connect Ashby and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis in one instruction to create a Google Calendar interview event from the Ashby request, using only details present in the request.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real interview request and check the resulting event.
Questions about this workflow
How does the workflow start?
An HTTP request to the Notis webhook starts it. Ashby has no listed native trigger events, so the Ashby process must send the request to that webhook.
Can it fill in missing interview times?
No. The workflow can use details available in the request. Supply any missing time or timezone in the request, or ask Notis to flag the request for review.
Does creating an event invite the candidate?
The listed Create Event action adds the organizer as an attendee by default. Candidate invitations depend on attendee details and event inputs being provided.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ashby to Google Calendar. A trigger fires from one place; an action lands in another.
Ashby 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.
Ashby 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.