Start implementation branches from slide proposals
Move from an approved implementation idea to a ready branch. Tell Notis which repository and starting commit to use, and it can create a uniquely named branch when a new slide captures the work.
Trigger
New Slide Added
Fires when a new slide is added to a Google Slides presentation.
Action
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.
Why this helps
Developers can lose momentum when an agreed proposal still needs a branch before implementation can begin.
- Reduce setup work between planning and implementation.
- Use a branch name based on the proposal's purpose.
- Start from a target commit supplied in the instruction or available context.
Setup
Build it in a few focused steps.
- 1Connect Google Slides and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to create a branch for a concrete implementation proposal, specifying the repository and target commit to use.
- 4Pick the Google Slides New Slide Added trigger and choose where run reports should go.
- 5Test with one real proposal slide and confirm the branch name and starting commit.
Questions about this workflow
Can the slide alone determine the starting commit?
The action requires a target commit hash. Specify it in your instruction or ensure it is available in the context Notis can use.
What happens if the branch name already exists?
The branch name must be unique. Instruct Notis to choose a distinctive name and report if it cannot create the branch.
Will this create a branch for every new slide?
Describe the condition clearly, such as creating a branch only when a slide contains a concrete implementation proposal.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Slides to Bitbucket. A trigger fires from one place; an action lands in another.
Google Slides 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 Slide Added
Fires when a new slide is added to a Google Slides presentation.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
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.
Google Slides 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.