Keep customer-impact signals connected to follow-up
Make the customer consequence visible in the engineering issue while the team still has the dashboard context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Customer-impacting trends are easy to lose when analytics, support conversations, and engineering work live in separate places.
- Connects a reported metric shift to customer-focused investigation work.
- Keeps the why and who may be affected alongside the issue.
- Helps reduce delay between noticing a trend and starting follow-up.
Setup
Build it in a few focused steps.
- 1Connect Tableau and Bitbucket to Notis once through the portal.
- 2Ask Notis to create an automation, or open Automations -> New Automation.
- 3Give Notis one plain-language instruction to create a Bitbucket issue for incoming alerts that describe customer impact.
- 4Select the webhook trigger and choose a channel for run reports.
- 5Test with one real customer-impact alert and review the issue for enough context to act.
Questions about this workflow
Does this contact affected customers?
No. It creates a Bitbucket issue for internal follow-up.
What if an alert has no customer detail?
Tell Notis in the prompt how to handle alerts with missing context, such as creating an issue that requests investigation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Tableau to Bitbucket. A trigger fires from one place; an action lands in another.
Tableau 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.
Tableau 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.