Turn deal blockers into clear product issues
Make a customer blocker visible to the people who can investigate it, with the deal context included from the start.
Trigger
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
Action
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.
Why this helps
A deal at risk because of a product limitation can stall while teams separately work out how to log and route the blocker.
- Create a focused record when a deal change surfaces a product limitation.
- Keep the available customer and deal context with the issue.
- Avoid opening issues for stage changes unrelated to product blockers.
Setup
Build it in a few focused steps.
- 1Connect HubSpot and Bitbucket once in the Notis portal.
- 2Create a named automation from Automations, then New Automation.
- 3Tell Notis to create a Bitbucket issue only when a deal stage update indicates a product blocker, summarizing the blocker and relevant deal context.
- 4Choose the HubSpot Deal Stage Updated trigger and choose where run reports go.
- 5Test with one real deal whose stage update describes a product blocker.
Questions about this workflow
Will every deal stage change open an issue?
No. Specify the stage changes or returned deal details that indicate a product blocker, and ask Notis to skip unrelated updates.
What happens if the blocker is unclear?
Ask Notis to report that the available deal information does not establish a clear product blocker, rather than creating a speculative issue.
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.