Skip to content
Notis

Turn recurring email themes into weekly issues

Give repeated customer pain a clear place in the engineering backlog.

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

The same problem can surface across multiple messages without anyone connecting the dots.

  • Make repeated feedback easier to spot across a review period.
  • Create a clear issue for a supported recurring problem.
  • Keep a regular feedback review from depending on memory.

Setup

Build it in a few focused steps.

  • 1Connect Agent Mail and Bitbucket once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3Tell Notis to review the email data made available to it, identify recurring problems, and create an issue for each supported theme.
  • 4Choose a recurring schedule and select where run reports should go.
  • 5Test with one real review period's email data.

Questions about this workflow

Can the schedule automatically retrieve all prior emails?

Only if the connected app provides that data to the automation. The schedule itself does not define an inbox search or filter.

What if a theme appears only once?

Tell Notis to create issues only for patterns supported by multiple messages or a threshold you provide.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Agent mail to Bitbucket. A trigger fires from one place; an action lands in another.

Agent mail triggers

Bitbucket actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New Email Received

Trigger for new emails in an AgentMail inbox

TriggerPolling

Create an issue comment

Adds a new comment with markdown support to an existing bitbucket issue.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Create snippet comment

Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.

ActionInstant

Delete issue

Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.

ActionInstant

Delete repository

Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.

ActionInstant

Connect any two apps with Notis in the middle.

Agent mail 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.