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.
Workflows do something in Gmail, instantly.
Pair pages are mirrored. Each direction gets its own dedicated page.
4 Bitbucket triggers wired to 27 Gmail actions. Most-used pairing: Issue Created → Add Labels to Message.
1 Gmail triggers wired to 10 Bitbucket actions downstream.
See Gmail → Bitbucket →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.
No code, no glue, no half-day setup. Each step is one click.
Open Tiny Command, authorize Bitbucket and Gmail once each. Both connections are available to every workflow on your account.
Drop the Bitbucket → Issue Created trigger onto the canvas. Tiny Command auto-registers the webhook.
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
Drop the Gmail → Add Labels to Message action below it. Map fields from the Bitbucket payload into the Gmail inputs.
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Free tier available. No credit card. No onboarding call.