Keep dashboard maintenance from becoming invisible work
Put stale dashboards and recurring breaks into the same queue where the repair can actually happen.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Analytics upkeep competes with product work, so stale dashboards can stay misleading long after their last review.
- Turns recurring maintenance review into visible engineering work.
- Keeps broken or outdated analytics assets from relying on memory.
- Creates follow-ups only for dashboards the prompt identifies as needing attention.
Setup
Build it in a few focused steps.
- 1Connect Tableau and Bitbucket to Notis once in the portal.
- 2Create the automation by asking Notis or opening Automations -> New Automation.
- 3Write one instruction asking Notis to identify stale or broken dashboards in its Tableau context and create Bitbucket maintenance issues.
- 4Choose a monthly or other suitable cron schedule and a channel for run reports.
- 5Try one known stale dashboard example and review the issue details.
Questions about this workflow
How does Notis decide a dashboard is stale?
Describe the criteria in the prompt and ensure the connected Tableau context or scheduled input makes those facts available.
Can I choose a monthly cadence?
Yes. Select a recurring cron schedule when creating the automation.
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.