Move approved work into Bitbucket review
Once a change is ready, get it into the review queue without reassembling the request by hand. Send the approval context through Ably.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Approved work can sit waiting because creating the pull request requires another round of context gathering and manual setup.
- Carry the approval context into the review request.
- Reduce the manual handoff from decision to code review.
- Make ready work visible in Bitbucket sooner.
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 approved changes.
- 3Describe that an approved request should create a Bitbucket pull request using the supplied existing source branch and review context.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one approved request and confirm the source branch and destination are correct.
Questions about this workflow
Does the source branch need to exist?
Yes. The Bitbucket action requires an existing source branch, and it must differ from the optional destination branch.
Can Notis determine whether work is approved?
The incoming request should clearly indicate approval. Do not send unapproved requests to this workflow.
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.