Surface open pull requests tied to an advancing deal
Give teams a focused view of open code changes when a customer opportunity reaches a stage where delivery readiness matters.
Trigger
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
Action
List pull requests
Lists pull requests in a specified, accessible bitbucket repository, optionally filtering by state (open, merged, declined).
Why this helps
A deal can advance while related code remains unreviewed, with no simple reminder to check the repository.
- Bring open code reviews into view when a deal reaches a relevant stage.
- Help teams spot delivery work that may need attention.
- Rely on a repository identifier available in the deal context.
Setup
Build it in a few focused steps.
- 1Connect HubSpot and Bitbucket once in the Notis portal.
- 2Create an automation through Automations, then New Automation.
- 3Tell Notis to list open pull requests for the Bitbucket repository identified in a deal when it reaches the chosen stage, then summarize the results in the run report.
- 4Choose the HubSpot Deal Stage Updated trigger and select a report channel.
- 5Test with one real deal that includes an identifiable repository.
Questions about this workflow
Does this approve or merge pull requests?
No. It lists open pull requests and summarizes them in the run report for a person to review.
What if the deal has no repository reference?
Ask Notis to report that it cannot identify a repository from the available deal data and avoid listing an unrelated repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to Bitbucket. A trigger fires from one place; an action lands in another.
Hubspot 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.
Contact Created Trigger
Contact Created Trigger
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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.
Hubspot 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.