Capture emailed technical decisions as Bitbucket issues
Put the engineering follow-up from a decision email straight into the repository backlog.
Trigger
Email Sent
Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.
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
Decisions sent by email can lose their follow-up when nobody creates a trackable task.
- Convert decisions into trackable follow-up work
- Keep next steps visible to engineering
- Reduce reliance on memory after sending an email
Setup
Build it in a few focused steps.
- 1Connect Gmail and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to identify actionable engineering decisions in sent emails and create a Bitbucket issue summarizing the follow-up.
- 4Pick Email Sent as the trigger and choose where run reports should go.
- 5Test with one real sent decision email.
Questions about this workflow
Will every sent email create an issue?
Describe that an issue should be created only when the message records an actionable engineering decision or follow-up.
Can the issue capture action items?
Ask Notis to summarize the decision and the follow-up needed from the email.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Gmail to Bitbucket. A trigger fires from one place; an action lands in another.
Gmail 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.
Email Sent
Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
New Gmail Message Received Trigger
Triggers when a new message is received in Gmail.
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.
Gmail 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.