Inspect the pull request connected to a customer deal
Bring the details of a customer linked pull request into the moment a deal changes stage, so the team can review the current code work.
Trigger
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
Action
Get Pull Request
Get a single pull request by id with complete details.
Why this helps
Teams may need to open Bitbucket and search manually to understand the pull request connected to a changing customer deal.
- Retrieve complete details for a specifically referenced pull request.
- Reduce context switching during deal review.
- Summarize returned information without inferring unprovided readiness.
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 retrieve and summarize the Bitbucket pull request id explicitly referenced in a deal whenever the deal stage updates.
- 4Choose the HubSpot Deal Stage Updated trigger and choose a run report destination.
- 5Test with one real deal that includes a valid pull request reference.
Questions about this workflow
Does the deal need a pull request id?
Yes. The action retrieves a single pull request by id. Ask Notis to report when the deal does not provide a valid reference.
Does this make a decision about the pull request?
It retrieves details and can summarize them. Any review decision should use criteria you supply and the information available in the returned details.
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.