Create a Bitbucket issue from every new Confluence page
Capture an idea or decision in Confluence and give it a clear home in Bitbucket.
Trigger
New Page Created
Triggers when a new page is created in Confluence. Optionally filters by space or status.
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
Important work gets documented in Confluence but never becomes a trackable engineering task.
- Reduce duplicate entry
- Keep documented decisions actionable
- Give every new page a visible follow-up
Setup
Build it in a few focused steps.
- 1Connect Confluence and Bitbucket in Notis once.
- 2Create an automation and describe that each new relevant page should become a Bitbucket issue.
- 3Pick the New Page Created trigger for Confluence.
- 4Choose where Notis should send run reports.
- 5Test it with one real Confluence page.
Questions about this workflow
Can Notis decide whether a page needs an issue?
Yes. Tell Notis what signals indicate actionable work in the automation instruction.
What if the page is informational only?
Instruct Notis to skip pages that do not contain a request, defect, decision, or follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Confluence to Bitbucket. A trigger fires from one place; an action lands in another.
Confluence 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.
New Attachment Added
Triggers when a new attachment is uploaded to a Confluence page. Optionally filters by media type.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Blog Post Added to Label
Triggers when a new blog post is added to a specific label in Confluence.
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.
Blogpost Inline Comment Added
Triggers when a new inline comment is added to a Confluence blog post.
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.
Blog Post Like Count Changed
Triggers when a Confluence blog post's like count changes (someone likes or unlikes).
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
Blog Post Updated
Triggers when a Confluence blog post is updated (any edit that creates a new version).
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Content Restrictions Changed
Triggers when view or edit restrictions change on a Confluence page or blog post. Detects user/group restrictions being added, removed, or modified.
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.
Confluence 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.