Connect 2chat to Bitbucket

When something happens in 2chat, Notis takes the next step in Bitbucket. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from 2chat to Bitbucket

View example

Turn a WhatsApp bug report into a Bitbucket issue

Send a webhook with a WhatsApp bug report and let Notis create a clear Bitbucket issue for follow-up.

View example

Add a WhatsApp update to a Bitbucket issue

Send a webhook with a relevant chat update and have Notis add a concise comment to an existing issue.

View example

Reflect a WhatsApp decision in a Bitbucket issue

Send a webhook with a confirmed decision and have Notis update the relevant issue details.

View example

Create a pull request from approved work

Use a webhook to ask Notis to open a Bitbucket pull request for work with known source and destination branches.

View example

Create a Bitbucket branch for approved work

Start a webhook for a defined task and have Notis create a uniquely named branch from the supplied target commit.

View example

Answer a chat question with Bitbucket file context

Send a webhook with a repository file question and have Notis retrieve the file at the requested commit or ref.

View example

Prepare a scheduled pull request review queue

On a schedule, have Notis list open Bitbucket pull requests and summarize the ones that need attention.

View example

Keep a scheduled Bitbucket repository inventory

On a recurring schedule, list accessible repositories in a workspace and summarize the inventory.

View example

Review Bitbucket workspace membership on a schedule

Have Notis periodically list workspace members and summarize the membership for a routine review.

Supported Triggers and Actions

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

2chat 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

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

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.