- Integrations
- /
- Bitbucket
- /
- with Gmail
Connect Bitbucket to Gmail in two minutes.
Real-time triggers from Bitbucket, ready-made actions in Gmail. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Bitbucket.
- Issue CreatedWebhook
- Pull Request CreatedWebhook
- Pull Request MergedWebhook
- Push to BranchWebhook
Workflows do something in Gmail, instantly.
- Add Labels to MessageAPI
- Create DraftAPI
- Create LabelAPI
- Delete DraftAPI
- Delete LabelAPI
- Delete MessageAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Bitbucket, do it in Gmail.
4 Bitbucket triggers wired to 27 Gmail actions. Most-used pairing: Issue Created → Add Labels to Message.
Or fire it the other way around.
1 Gmail triggers wired to 10 Bitbucket actions downstream.
See Gmail → Bitbucket →Common Bitbucket → Gmail workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new issue is created in a Bitbucket repository. Payload includes the issue title, body, reporter, labels, and milestone if assigned. Useful for "auto-route issues to the right team channel" or "create matching Linear/Jira issue for cross-tracker sync" workflows.
Fires when a new issue is created in a Bitbucket repository. Payload includes the issue title, body, reporter, labels, and milestone if assigned. Useful for "auto-route issues to the right team channel" or "create matching Linear/Jira issue for cross-tracker sync" workflows.
Fires when a new issue is created in a Bitbucket repository. Payload includes the issue title, body, reporter, labels, and milestone if assigned. Useful for "auto-route issues to the right team channel" or "create matching Linear/Jira issue for cross-tracker sync" workflows.
Fires when a new issue is created in a Bitbucket repository. Payload includes the issue title, body, reporter, labels, and milestone if assigned. Useful for "auto-route issues to the right team channel" or "create matching Linear/Jira issue for cross-tracker sync" workflows.
Fires when a pull request opens in a Bitbucket repository. Payload includes the source/destination branches, title, author, and reviewers. The base hook for "auto-assign reviewers", "post to Slack PR-review channel", "trigger CI on PR-open" workflows.
Fires when a pull request opens in a Bitbucket repository. Payload includes the source/destination branches, title, author, and reviewers. The base hook for "auto-assign reviewers", "post to Slack PR-review channel", "trigger CI on PR-open" workflows.
Fires when a pull request opens in a Bitbucket repository. Payload includes the source/destination branches, title, author, and reviewers. The base hook for "auto-assign reviewers", "post to Slack PR-review channel", "trigger CI on PR-open" workflows.
Fires when a pull request opens in a Bitbucket repository. Payload includes the source/destination branches, title, author, and reviewers. The base hook for "auto-assign reviewers", "post to Slack PR-review channel", "trigger CI on PR-open" workflows.
Fires when a PR merges to its destination branch. Useful for "auto-deploy main on merge", "transition the related Jira issue to Resolved", "send the PR contributor a thanks note" downstream automations.
Connect Bitbucket and Gmail in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Bitbucket and Gmail
Open Tiny Command, authorize Bitbucket and Gmail once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Bitbucket trigger
Drop the Bitbucket → Issue Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/bitbucket.trigger-issue-created - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Gmail action
Drop the Gmail → Add Labels to Message action below it. Map fields from the Bitbucket payload into the Gmail inputs.
google-gmail.add-labels - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Bitbucket + Gmail.
How long does it take to connect Bitbucket and Gmail on Tiny Command?
Is the Bitbucket ↔ Gmail integration real-time?
Can I filter or transform data between Bitbucket and Gmail?
What Bitbucket events can trigger a Gmail workflow?
Do I need a paid plan to use Bitbucket with Gmail?
What if I want Gmail → Bitbucket instead?
Other apps that pair well with Bitbucket.
Wire Bitbucket to Gmail in 2 minutes.
Free tier available. No credit card. No onboarding call.