Check Bitbucket control files against 21risk expectations
Spot drift in a policy or configuration file before it becomes a compliance surprise.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get file from repository
Retrieves a specific file's content from a bitbucket repository at a given commit (hash, branch, or tag), failing if the file path is invalid for that commit.
Why this helps
Control files can change quietly between formal audits, leaving teams unaware of drift.
- Catches file drift earlier
- Creates a repeatable control check
- Turns technical changes into a readable report
Setup
Build it in a few focused steps.
- 1Connect 21risk and Bitbucket once.
- 2Create an automation and provide the control expectation in plain language.
- 3Pick a notis_cron schedule and choose where run reports go.
- 4Test with one repository file at a known commit or branch.
Questions about this workflow
What expectation does Notis compare against?
You provide the expected control or baseline in the automation instruction. Notis cannot infer a standard that 21risk or Bitbucket does not return.
Can it read any file?
It can retrieve a specified file when the repository, path, and commit, branch, or tag are valid.
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.