Keep changing customer commitments visible to product
When customer expectations shift, update the issue discussion that tracks the work connected to the deal.
Trigger
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
Action
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Why this helps
A changed commitment can leave engineering working from stale expectations if the update stays only in the CRM.
- Bring a changed customer expectation to the related issue discussion.
- Make the reason for a deal stage change easier to understand.
- Use only commitment changes present in the deal data.
Setup
Build it in a few focused steps.
- 1Connect HubSpot and Bitbucket once in the Notis portal.
- 2Create a named automation in Automations, then New Automation.
- 3Tell Notis to comment on the issue identified by a deal when a stage update changes a customer commitment, summarizing the prior and current expectation only when both are available.
- 4Choose HubSpot Deal Stage Updated and select where run reports should go.
- 5Test with one real deal that contains a commitment change and a related issue reference.
Questions about this workflow
Does this compare deal history?
Only if the trigger data or available deal context provides the relevant prior and current commitment. Ask Notis to report when that comparison cannot be made.
What if the stage changed but the commitment did not?
Instruct Notis to skip the comment unless the available information indicates a changed customer commitment.
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.