Create a Bitbucket branch from every 21risk audit finding
Move from a compliance finding to a ready-to-use coding branch before the context gets lost.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Audit findings can sit in a compliance tool while the engineering work needed to address them remains unstarted.
- Starts remediation with one plain-language request
- Keeps branch names tied to audit context
- Reduces follow-up between compliance and engineering
Setup
Build it in a few focused steps.
- 1Connect 21risk and Bitbucket in the Notis portal.
- 2Create a new automation and describe the branch outcome in one instruction.
- 3Choose a notis_webhook trigger for incoming 21risk data.
- 4Select where run reports should go, then test with one real audit finding.
Questions about this workflow
What does the webhook need to include?
Include enough audit context for Notis to identify the repository, target commit, and a unique branch name. If any of those are missing, Notis should report what is needed.
Does this change code automatically?
No. It creates the Bitbucket branch so a person or another approved workflow can make the fix.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Bitbucket. A trigger fires from one place; an action lands in another.
21risk 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.
21risk 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.