Bitbucket Push Event Listener (Foundation Template)

Overview

This workflow provides a minimal yet production-ready foundation for listening to Bitbucket repository push events. It triggers automatically whenever code is pushed to a specified repository, making it an ideal starting point for building CI/CD pipelines, deployment automation, notification systems, or any other custom workflow that reacts to code changes. An integrated error handler ensures the workflow fails gracefully and can be extended with additional error reporting.

Workflow Nodes

• Bitbucket Trigger (OAuth2 auth) — Listens for repo:push events on a Bitbucket repository. Configured parameters:
  • events: ["repo:push"] — Only triggers on push events (other event types like pull requests can be added).
  • resource: "repository" — Monitors changes at the repository level.
  • repository: "test" — The Bitbucket repository slug to watch (should be updated to your actual repository name). This node acts as a webhook receiver. It requires authentication via n8n's built-in Bitbucket OAuth2 integration (or a personal access token) to register and manage the webhook automatically.
• Error Handler (No auth) — type stopAndError. If any node during execution fails, this handler stops the workflow and logs the error message "Workflow execution error". It does not require external credentials and serves as a safety net to prevent silent failures.

Note: As provided, the nodes are not connected (no data flows between them). The workflow is a structural template—you must add additional nodes (e.g., HTTP Request, Slack, Jira) after the trigger to actually process the event payload.

Setup Instructions

1. Bitbucket Account & Repository – Ensure you have a Bitbucket account and a repository (public or private) that you want to monitor.
2. n8n Bitbucket Credentials – In n8n, go to Credentials > New > Bitbucket OAuth2. Follow the OAuth flow to authorize n8n to access your Bitbucket account. Alternatively, you can use a Bitbucket App Password with appropriate permissions (though OAuth2 is recommended).
3. Configure the Trigger – Open the Bitbucket Trigger node and update the repository field to your actual repository slug (e.g., my-project). Leave other parameters as default unless you need different events.
4. Deploy & Test – Activate the workflow. Push a commit to the repository; the trigger should fire. If no additional nodes are connected, the workflow will end immediately (which is expected).

Use Cases & Adaptations

• Continuous Integration – Add an HTTP Request node to call a Jenkins or GitHub Actions API to trigger a build.
• Deployment Automation – Connect a Docker or SSH node to deploy the latest code to a staging or production server.
• Notifications – Use a Slack or email node to alert the team of new pushes with commit details.
• Issue Tracking – Post a comment to a Jira issue linked to the commit.
• Code Quality – Run a linter or test suite via a command node and report results.

To adapt, simply append new nodes after the trigger and map fields from the Bitbucket event payload (e.g., {{ $json.push.changes[0].new.name }} for the branch name). You can also change the events parameter to listen for pull request creation, branch deletion, or other Bitbucket webhook events.

{
  "nodes": [
    {
      "name": "Bitbucket Trigger",
      "type": "n8n-nodes-base.bitbucketTrigger",
      "position": [
        880,
        390
      ],
      "webhookId": "97ca8044-5835-4547-801d-c27dd7f10c2d",
      "parameters": {
        "events": [
          "repo:push"
        ],
        "resource": "repository",
        "repository": "test"
      },
      "credentials": {
        "bitbucketApi": "bitbucket_creds"
      },
      "typeVersion": 1,
      "id": "8712679c-947e-4360-970b-e7aebff77c83",
      "notes": "This bitbucketTrigger node performs automated tasks as part of the workflow."
    },
    {
      "id": "error-c568f4ba",
      "name": "Error Handler",
      "type": "n8n-nodes-base.stopAndError",
      "typeVersion": 1,
      "position": [
        1000,
        400
      ],
      "parameters": {
        "message": "Workflow execution error",
        "options": {}
      }
    }
  ],
  "connections": {},
  "name": "Bitbuckettrigger Workflow",
  "description": "Automated workflow: Bitbuckettrigger Workflow. This workflow processes data and performs automated tasks.",
  "settings": {
    "executionOrder": "v1",
    "saveManualExecutions": true,
    "callerPolicy": "workflowsFromSameOwner",
    "errorWorkflow": null,
    "timezone": "UTC",
    "executionTimeout": 3600,
    "maxExecutions": 1000,
// ... truncated (copy to see full JSON)