Create an onboarding issue for every new organization
Start account setup with a clear checklist the team can execute.
Trigger
New Organization Received Trigger
Triggered when a new organization is created in Pipedrive
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
New organizations are recorded in sales systems without a reliable technical onboarding queue.
- Standardizes technical onboarding
- Makes dependencies visible
- Reduces missed setup tasks
Setup
Build it in a few focused steps.
- 1Connect Pipedrive and Bitbucket in Notis once.
- 2Create an automation named Organization Onboarding Issue.
- 3Tell Notis to create a Bitbucket issue with an onboarding checklist based on the organization details and known requirements.
- 4Pick the New Organization Received trigger and choose a run report channel.
- 5Test with one real organization and verify the checklist.
Questions about this workflow
Can onboarding vary by organization type?
Yes. Tell Notis to tailor the checklist using the organization details provided by Pipedrive.
Can it flag missing onboarding information?
Yes. Ask Notis to list missing details at the top of the issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Pipedrive to Bitbucket. A trigger fires from one place; an action lands in another.
Pipedrive 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 Deal Received Trigger
Triggered when a new deal is created in Pipedrive
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
New Note Received Trigger
Triggered when a new note is created in Pipedrive
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 Organization Received Trigger
Triggered when a new organization is created in Pipedrive
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.
Pipedrive 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.