Create follow-up for pending Box collaboration invites
An invite can sit pending while a project waits. Have Notis create a Bitbucket follow-up issue with the invite context and next step.
Trigger
New Pending Collaboration Invite
Triggers when a new pending collaboration invite is created. This trigger monitors the user's pending collaborations and fires when new pending collaboration invites are detected.
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
Pending access invites can block project work without a visible reminder in the team's engineering tracker.
- Make pending access visible to project owners
- Create a home for onboarding follow-up
- Reduce the chance that an invite blocks work unnoticed
Setup
Build it in a few focused steps.
- 1Connect Box and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, then enter a name and prompt.
- 3Tell Notis to create a Bitbucket issue for each new pending invite with its context and a practical follow-up step.
- 4Pick the Box New Pending Collaboration Invite trigger and choose where run reports should go.
- 5Test with one real pending invite and review the issue.
Questions about this workflow
Does this trigger cover pending invites across Box?
It monitors the user's pending collaborations and detects new pending invites.
Can the issue be assigned?
You can ask Notis to assign it to a Bitbucket user, provided that person has repository access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Box to Bitbucket. A trigger fires from one place; an action lands in another.
Box 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.
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Comment Changed
Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.
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.
New File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
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.
File Metadata Changed
Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
File Shared Link Changed
Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
New File Version Uploaded
Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.
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.
Box 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.