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.

2 nodesmanual triggerDevOps
Stop And Error

Workflow JSON

{
  "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)

How to Import This Workflow

  1. 1Copy the workflow JSON above using the Copy Workflow JSON button.
  2. 2Open your n8n instance and go to Workflows.
  3. 3Click Import from JSON and paste the copied workflow.

Don't have an n8n instance? Start your free trial at n8nautomation.cloud

Related Templates

Automated n8n Workflow Backup to GitHub Repository

Overview This workflow automatically backs up every workflow in your n8n instance to a dedicated GitHub repository. It runs on a configurable schedule (or manually) and ensures that all your workflow JSON files are version-controlled and safely stored in a structured folder. The backup process intelligently handles both new workflows (creates a file) and existing ones (updates the file), making it ideal for disaster recovery, collaboration, or tracking changes over time. Step-by-Step Node Breakdown Schedule Trigger (No additional auth) — Triggers the workflow on a recurring interval. By default it runs hourly, but you can customize the schedule (e.g., daily at midnight) to suit your needs. Also supports manual execution via the Manual Trigger node. Manual Trigger (No auth) — Provides a manual button to run the backup immediately, useful for testing or on-demand backups. Get many workflows (Internal n8n API, no external credentials) — Fetches a list of all workflows from your n8n instance using the built-in n8n node. No separate API key is required; it uses the same authentication as your n8n session. Loop Over Items (No auth) — Iterates over each workflow in the list one at a time. This node processes workflows sequentially, preventing race conditions. Getafile (GitHub, OAuth2 / Personal Access Token) — Attempts to retrieve the existing workflow file from your GitHub repository at the path . If the file does not exist (i.e., a new workflow), the node’s error output is triggered. The expression in sanitizes the workflow name by replacing invalid characters (), converting to , and normalizing spaces. Convert to File1 (No auth) — Converts the retrieved GitHub file’s binary data back to a JSON object so it can be compared or overwritten. Extract from File1 (No auth) — Extracts the JSON content from the binary file, preparing it for an update operation. Edit a file (GitHub, OAuth2 / Personal Access Token) — If the workflow already exists on GitHub, this node updates the file with the latest JSON from your n8n instance. The commit message is dynamically generated (e.g., ). Convert to File (No auth) — Converts the current n8n workflow JSON into a binary file () with the workflow’s name as the filename. Create a file (GitHub, OAuth2 / Personal Access Token) — If the workflow is new (i.e., error output), this node creates a new file in the folder. The commit message includes the workflow name and . The workflow loops back to the Loop Over Items node to process the next workflow. The Sticky Note at the top serves as a comment. Setup Instructions GitHub account — You need a GitHub account and a repository (e.g., ) to store the backups. Create an empty repository or use an existing one. GitHub credential in n8n — Add a GitHub OAuth2 or Personal Access Token credential in n8n under Credentials > GitHub. Ensure the token has scope (or at least and ). Configure the nodes — - In Get many workflows, no changes needed. - In Getafile, Create a file, and Edit a file, update the and fields to match your GitHub username and repo name. - Optionally adjust the Schedule Trigger interval (set hours/minutes as desired). Error handling — The workflow references an external error workflow (). If you don’t have that, you should either create a simple error handler or remove the setting in the workflow settings. Use Cases & Adaptations Disaster recovery — Restore all workflows by downloading the JSON files from GitHub and importing them back into n8n. Version history — Track changes to workflows over time via GitHub commits and diffs. Multi-instance sync — Modify the workflow to run on multiple n8n instances, pushing to the same repo (be cautious with conflicts). Selective backup — Add a filter node after to only backup workflows with a specific tag or name pattern. Notification — Insert a Slack or email node after the loop to notify you when a backup completes or if an error occurs.

11 nodes

n8n Upgrade: Detect Affected Workflows with Broken Connections

Summary This workflow helps n8n administrators identify workflows that may have been affected by a past upgrade (specifically n8n version ) where multi-output nodes (like , , ) could have their output connections accidentally re-wired. It provides a self-service webhook endpoint that returns an HTML report listing all workflows with potentially broken connections, making it easy to audit and fix them. Node-by-Node Walkthrough Webhook (No auth) — Listens for HTTP GET requests at the path . When a user visits this URL in their browser, the workflow is triggered. The response mode is set to "Response Node", meaning the final output will be sent back directly. Get all workflows (API Key auth) — Uses the n8n API to fetch all workflows from the instance. You must configure this node with an n8n API credential (a personal access token created under Settings > n8n API). The node has no filters, so it retrieves every workflow. Parse potentially affected workflows (Code node, no auth) — A JavaScript code node that loops through each workflow, inspects its connections, and checks if any multi-output node (defined in the array) has empty outputs. If a node has fewer connected outputs than expected, it is flagged as potentially affected. The node outputs a JSON object with an array of affected workflows, each containing , , , and . Generate Report (HTML node, no auth) — Creates a static HTML document with a styled container, a heading, and an empty list. This serves as the shell for the interactive report generated by the next node. Serve HTML Report (Respond to Webhook node, no auth) — Takes the HTML template from the previous node and injects JavaScript that parses the affected workflows data (from the code node) and dynamically builds a list of clickable links. Each link opens the workflow in a new tab so the admin can inspect and fix the connections. The response headers are set to . Setup Instructions Prerequisites: You must have admin access to the n8n instance (the workflow must be run by the instance owner). Create an n8n API key: Go to Settings > n8n API in your n8n instance and generate a personal access token. Copy the token. Configure the "Get all workflows" node: Add an n8n credential of type "API Key" and paste the token. Leave the filters empty. Customize multi-output nodes (if needed): The code node contains a list with the default nodes (, , ). If you have community nodes with multiple outputs, add them to this array with their correct output count. Activate the workflow: Toggle the workflow to active. Use the report: Open your browser and navigate to . The page will list all affected workflows. Click on a row to open the workflow in a new tab — inspect the connections and re-wire them if needed. Use Cases & Variations Post-upgrade audit: Run this workflow after every n8n upgrade to catch connection issues early. Customized detection: Extend the array in the code node to include any custom node type that has multiple outputs. Slack/Email notification: Instead of serving an HTML report, you could send the list of affected workflows to a Slack channel or email using additional nodes. Scheduled scanning: Replace the Webhook trigger with a Schedule trigger to run the check daily and automatically notify the admin.

9 nodes

Disk Space Watchdog with Tiered Thresholds and Telegram Alert

Summary This workflow monitors disk usage on a remote Linux server via SSH, applying tiered thresholds (warning and critical) to avoid alert fatigue. It tracks the last known state of each mount point using n8n's workflow static data, so you only receive a notification when a disk changes level (e.g., from OK to warning, or from critical back to OK). Alerts are sent first to a Telegram chat; if that fails, an email is sent as a reliable fallback. The workflow is fully configurable through environment variables, making it easy to adapt without editing the code. Step-by-Step Nodes Schedule Trigger (No auth) — Runs the workflow every 30 minutes. Configured via rule with minutes interval = 30. Check Disk Usage (SSH) (SSH auth – key or password) — Executes the command on the remote server. You must provide credentials (username + SSH key or password) stored in an n8n credential of type "SSH". Parse & Evaluate (No auth) — A Code node that parses the from the SSH command. It reads thresholds from environment variables ( and , defaulting to 80% and 90%). For each mount point: - Compares usage percentage against thresholds. - Uses to remember the last known level (ok / warning / critical). - Only emits an alert when the level changes (including recovery messages when a disk returns below threshold). - Outputs . Any alerts? (No auth) — An IF node that checks (boolean true). If true, execution goes to the Telegram branch; otherwise the workflow ends silently. Send Telegram Alert (Telegram API – Bot Token auth) — Sends the alert message to a Telegram chat. The chat ID is read from . The node is set to (on error -> next output). On success, no further action. On error, execution flows into the email fallback. Send Email Fallback (SMTP auth – username/password or OAuth2) — Sends the same alert message via email. Uses and for sender and recipient. This ensures alerts are never lost if Telegram is down. Setup Instructions Prerequisites: - A Linux server with SSH access and passwordless sudo (if needed) or a user that can run . - A Telegram bot (create one via @BotFather) and obtain its API token. - A Telegram chat ID (can be a group or your own ID). - An SMTP server (e.g., Gmail, SendGrid, or your own) for email fallback. Environment Variables: Set the following in your n8n environment (e.g., or n8n UI > Workflow > Settings): - (default 80) - (default 90) - (e.g., ) - (e.g., ) - (e.g., ) Create Credentials in n8n: - SSH: Add a credential of type "SSH" with the server host, port (22), username, and either password or private key. - Telegram: Add a credential of type "Telegram API" with the bot token. - SMTP: Add a credential of type "SMTP" with server, port, user, password (and choose authentication method). Bind the credentials to the corresponding nodes in the workflow editor. Use Cases & Variations Server Fleet Monitoring: Duplicate the SSH node or use a loop to check multiple servers; aggregate results in the Code node. Different Thresholds per Mount: Extend the Code node to read a JSON mapping from an env variable or static data. Escalation Chain: Instead of email fallback, add a PagerDuty or Slack node on error. Silence Recoveries: Modify the Code node to skip recovery messages (remove the branch). Run less Frequently: Change the Schedule Trigger to hourly or daily. Add Grafana/Prometheus integration: Replace the SSH node with an HTTP request to your monitoring API. This workflow is ideal for sysadmins and DevOps teams who need reliable, noise‑free disk monitoring without a full‑blown observability stack.

6 nodes

Ready to automate with n8n?

Get affordable managed n8n hosting with 24/7 support.