Extend Your Calendar with Custom Webhooks
When external systems send events via webhook, Notis instantly creates matching calendar entries, bridging your calendar with any custom workflow.
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
Founders using custom tools, homegrown systems, or niche apps often can't connect them to Google Calendar, forcing manual entry or lost event data.
- Connect custom and niche tools to your calendar without integrations
- Automate calendar updates from any system that can make HTTP requests
- Eliminate manual entry for events from custom workflows
- Build flexible integrations tailored to your unique tech stack
Setup
Build it in a few focused steps.
- 1Connect Google Calendar in Notis Integrations.
- 2Create an automation: 'When an HTTP request arrives with event details, create a calendar event.'
- 3Set the trigger to 'Notis Webhook' and Notis will provide your unique webhook URL.
- 4Configure your external system to send POST requests to that webhook with event data (title, date, description).
- 5Test by sending a webhook request and verify the calendar event appears.
Questions about this workflow
What data should my webhook payload include?
At minimum: title and start date/time. You can also include description, end time, and attendee email addresses. Notis will map these to calendar event fields.
Can I customize how the webhook data maps to calendar events?
Yes. Describe your webhook structure and desired mapping in your automation prompt, and Notis will handle it.
Is this secure?
Your webhook URL is unique and should be treated like an API key. Only share it with trusted systems, and Notis provides authentication options.
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 985+ 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.