Bitbucket Make integrationAutomate Bitbucket with Make.
Can Make react the moment something happens in your Bitbucket repository? Yes. The Bitbucket Make integration gives you 10 modules, including 2 instant triggers. This guide connects your account and walks you through a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Bitbucket Make integration do for you?
The Bitbucket Make integration links your Bitbucket account to Make, a visual tool where you build a scenario (the automation itself) out of modules (one brick each: a trigger, an action or a search). Bitbucket brings 10 modules: 2 instant triggers, 6 actions and 2 searches, all usable without writing code.
Tell the right people about repository activity. Pair Watch a Repository with List Repository Watchers and every event on a repository comes with the list of people following it, ready to pass to a chat or email module from another app.
Keep a shared library of snippets in view. List Snippets returns every snippet your account can see, and Get a Snippet fetches a single one, so a scenario can copy them into a spreadsheet or a knowledge base.
Feed build files to the next step. Get a File returns the contents of a download artifact, not just its description, so a later module can store or send the file itself.
The list stops at 10 modules. For anything else in the Bitbucket API, Make an API Call reuses the same connection. Bitbucket also has an n8n node, described on the Bitbucket n8n integration page, and the n8n vs Make comparison sets both tools side by side. New to the editor? The Make training starts from zero.
How do you connect Bitbucket to Make?
- 01
Add a Bitbucket module
Log in to Make, open a scenario and add any Bitbucket module. Click Create a connection. With an instant trigger, Make first asks you to click Create a webhook, then Create a connection.
- 02
Name the connection
The Connection name field is optional, but a clear label such as the workspace name helps later when several accounts sit side by side. A connection is your Bitbucket account linked to Make once and reused by every Bitbucket module.
- 03
Enter your credentials
You need an active Bitbucket account and credentials such as OAuth 2.0 or API tokens. Paste the credentials copied from Bitbucket, or follow the instructions Make shows on screen, and the connection is saved.
Your first scenario with Bitbucket
GoalWhen something happens on a Bitbucket repository, Make fetches the list of people who watch that repository.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Bitbucket and pick Watch a Repository.
- 02
Set up the webhook
Click Create a webhook, then Create a connection to link your account. Once connected, Make lists what it can read, so you pick the repository to follow instead of typing it.
- 03
Add the watcher search
Click the + on the right of the trigger and add List Repository Watchers. Map the repository from the trigger output so the search always targets the repository that fired.
- 04
Test with Run once
Click Run once, then trigger an event in the repository. Open the bubble above each module to read the bundles it received: one per watcher on the search side.
- 05
Switch it on
When the test looks right, add the module of the app that should receive the list, then switch the scenario on. From now on, Bitbucket calls Make each time the repository sees an event.
Which Bitbucket triggers start a scenario?
2 modules start a scenario when something happens in Bitbucket. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Bitbucket as soon as it happens.
Watch a Repository
Instant triggerIn Make“Creates a new webhook on the specified repository.”
You get a scenario that wakes up on activity in one repository, because the module registers a webhook on that repository for you. There is nothing to build on the Bitbucket side: Make creates the hook when you set up the trigger.
Watch a Workspace
Instant triggerIn Make“Creates a new webhook on the specified workspace.”
This trigger covers a whole workspace from one place: Make places a webhook on the workspace, so activity across it lands in a single scenario instead of one per repository.
What can the Bitbucket modules do?
Bitbucket gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Snippet Comment
ActionIn Make“Creates a new comment on a Snippet.”
Posts a comment on a snippet for you, so the discussion stays next to the code it is about instead of in a side channel.
Get a File
ActionIn Make“Return a redirect to the contents of a download artifact. This endpoint returns the actual file contents and not the artifact's metadata.”
Hands the next module the actual contents of a download artifact, not its metadata, which is what you need to store or forward the file itself.
Get a Snippet
ActionIn Make“Retrieves a single snippet.”
Pulls one snippet you already know, by its identifier, and returns it as a single bundle (one item passed to the next module).
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Opens the rest of the Bitbucket API to your scenario with the connection you already set up, so no extra login is needed for endpoints the other modules skip.
Start Watching a Snippet
ActionIn Make“Start watching a specific snippet.”
Adds the connected account to the watchers of a snippet, so the follow is set by the scenario at the right moment rather than by hand.
Stop Watching a Snippet
ActionIn Make“Stops watching a specific snippet.”
Removes the connected account from a snippet's watchers, which cleans up follows that no longer serve any purpose without opening Bitbucket.
List Repository Watchers
SearchIn Make“Returns all watchers on the specified repository.”
Returns everyone who follows a repository, one bundle per person, which gives you a ready audience for a notification or a report.
List Snippets
SearchIn Make“Returns all snippets.”
Brings back all the snippets the connection can see, so a scenario can take stock of shared code without anyone copying links by hand.
Need help automating Bitbucket with Make?
A person reads every message.
