Make customer bug reports easier to triage
Customer feedback often arrives between conversations. Send a report through Ably and give it a clear next step in Bitbucket.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Customer reports can disappear into chat history before someone has time to turn them into engineering work.
- Capture customer wording without retyping it.
- Keep environment details attached when the report includes them.
- Give the team one place to review follow-up work.
Setup
Build it in a few focused steps.
- 1Connect Ably and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for customer bug intake.
- 3Describe that incoming customer bug reports should become Bitbucket issues with the report and supplied environment details.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real customer report and check the resulting issue.
Questions about this workflow
Does this workflow assume a particular customer support tool?
No. The request sent to the Notis webhook needs to include the customer report and any context you want preserved.
Will it assign an issue automatically?
Only if you describe a specific assignment rule and the assignee has access to the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to Bitbucket. A trigger fires from one place; an action lands in another.
Ably 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.
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.
Ably 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.