Make space to follow up on stalled pull requests
Tell Notis what counts as stale and which repositories to check. It can create a follow-up block when matching pull requests need attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Pull requests waiting on a response can fade from view when no one has reserved time to follow up.
- Turn a stated staleness rule into protected follow-up time.
- Keep relevant pull request references with the event.
- Reduce manual checking for work that may be waiting.
Setup
Build it in a few focused steps.
- 1Connect Bitbucket and Google Calendar once in Notis.
- 2Create an automation in plain language or in Automations, New Automation.
- 3In one instruction, define the staleness rule and repository scope, then ask Notis to create a follow-up block for matching pull requests.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real pull request that meets your stated rule.
Questions about this workflow
Does Bitbucket provide a universal definition of stale?
No staleness rule is assumed here. State the age or other criteria in the instruction so Notis can apply the rule to available Bitbucket data.
How should repeated runs avoid duplicate blocks?
Ask Notis to search for a matching calendar event before creating one, using the pull request reference, and report uncertain matches.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitbucket to Google Calendar. A trigger fires from one place; an action lands in another.
Bitbucket 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.
Bitbucket 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.