Keep open pull requests visible in your Ably channel
A short scheduled review can surface work waiting for attention, without requiring everyone to remember to check the repository.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List pull requests
Lists pull requests in a specified, accessible bitbucket repository, optionally filtering by state (open, merged, declined).
Why this helps
Open pull requests can sit unnoticed when the team relies on memory to revisit Bitbucket throughout the day.
- Surface open review work at a predictable time.
- Reduce context switching between chat and repository.
- Make the digest useful by focusing on the chosen repository.
Setup
Build it in a few focused steps.
- 1Connect Ably and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for the pull request digest.
- 3Describe that the automation should list open pull requests in the specified repository and send a concise digest through Ably.
- 4Pick the recurring schedule trigger and choose where run reports should go.
- 5Test with one real repository and confirm the digest contains its current open pull requests.
Questions about this workflow
Can the workflow include merged or declined requests?
This workflow is intended to focus on open requests. You can describe a different supported state if your review routine needs it.
Does it know which repository to inspect?
Specify the workspace and repository in the automation instructions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to Bitbucket. A trigger fires from one place; an action lands in another.
Ably triggers
Bitbucket actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a branch
Creates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Create a pull request
Creates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
Create repository
Creates a new bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project key` is not provided.
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Delete repository
Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.
Connect any two apps with Notis in the middle.
Ably and Bitbucket, 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 Bitbucket.