Give important weekly KPI changes a follow-up owner
Turn the weekly numbers review into a short list of investigate-next issues instead of another mental checklist.
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
Founders often spot meaningful KPI movement during a review but have to remember later to create engineering follow-up.
- Makes recurring KPI review produce concrete follow-up records.
- Keeps material changes from lingering as notes or open browser tabs.
- Lets the automation skip routine movement when the prompt defines what merits attention.
Setup
Build it in a few focused steps.
- 1Connect Tableau and Bitbucket to Notis once through the portal.
- 2Create a new automation in the portal or ask Notis conversationally.
- 3Tell Notis to review the available Tableau KPI summary and create an issue only for changes needing investigation.
- 4Pick a weekly cron schedule and a channel for run reports.
- 5Run one real weekly summary through the prompt and review the resulting issue.
Questions about this workflow
Can the schedule choose which KPI changes matter?
Yes. State the decision rule in the single plain-language automation prompt; there is no separate field-mapping screen.
Does Tableau need to send an alert for this workflow?
No. Notis starts it on the schedule you choose and uses the connected Tableau context available to it.
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.