Back to Blog

Try n8n free for 10 days — no charge until day 11 on select plans

Or skip the trial and start from $4/mo today

n8nMetabaseintegrationautomationanalytics

n8n + Metabase Integration: 5 Powerful Workflows You Can Build

n8nautomation TeamAugust 9, 2026

Data without action is just a collection of numbers on a screen. While Metabase excels at visualizing databases and turning complex SQL queries into intuitive dashboards, keeping your eyes glued to those charts all day is a poor use of your time. By integrating Metabase with n8n, you bridge the gap between static business intelligence and real-time operational response. This guide explores five high-impact automation workflows that extract raw insights from Metabase and instantly pipe them into Slack, HubSpot, ClickUp, and other essential tools in your business stack. Best of all, running these heavy reporting automations on a managed platform like n8nautomation.cloud ensures your workflows execute reliably without putting an unnecessary burden on your core database infrastructure.

How to Connect Metabase to n8n

Establishing a connection between Metabase and n8n requires setting up authentication credentials. This allows n8n to make secure HTTP API calls to fetch question results, update dashboard metrics, or execute SQL queries. Follow these three steps to connect your instances safely.

Step 1: Generate your Metabase API Key

To authenticate, you need a personal API token or your user credentials (username and password). In Metabase, API keys are tied to specific user accounts and inherit their database permissions. If you use SSO or want to isolate your automation traffic, create a dedicated bot user in Metabase.

  1. Log into your Metabase instance as an administrator or the dedicated service account.
  2. Navigate to the Admin Settings by clicking your profile icon in the top right corner.
  3. Click on the 'People' tab, then select 'Personal Access Tokens'.
  4. Click 'Create a token', give it a descriptive label such as 'n8n Integration Token', and copy the generated key immediately. Store it securely, as Metabase will not show this value again.

Step 2: Configure Credentials inside n8n

With the API key or login credentials copied, configure your n8n workspace to communicate with Metabase.

  1. Open your n8n dashboard and click on the 'Credentials' tab on the left sidebar.
  2. Click 'Add Credential' in the top right corner.
  3. Search for 'Metabase' and select it. If you are using standard HTTP requests to handle custom API payloads, you can also use 'Header Auth' or 'Basic Auth'.
  4. Enter your Metabase URL (for example, https://metabase.yourcompany.com). Make sure to exclude trailing slashes to prevent endpoint resolution errors.
  5. Paste the API token into the token field. If you are using username/password auth, input the respective credentials in the email and password fields.
  6. Click 'Save' to securely encrypt and store the credential on your instance.

Step 3: Test with a Simple Question Node

To ensure the connection works, test it with a simple data retrieval operation.

  1. Create a new workflow in n8n.
  2. Add the 'Metabase' node to your canvas.
  3. Select your newly created credential from the dropdown menu.
  4. Set the 'Resource' to 'Question' and the 'Operation' to 'Get' or 'Execute'.
  5. Enter a known Question ID from your Metabase environment (look at the URL of any question in your browser; the number at the end is the ID).
  6. Click 'Execute Node' to verify that n8n successfully receives the data payload from Metabase.

Tip: If the default Metabase node returns an empty JSON object when retrieving a question, it is usually because the question contains unsaved parameters or requires a complex card query. You can bypass this by using the n8n HTTP Request node to POST to the /api/card/:id/query endpoint with an empty JSON body {} in the request payload.

Workflow 1: Slack Alerts for DAU Drops

How It Works

This workflow automates infrastructure monitoring and alert routing by checking your Daily Active Users (DAU) metric at regular intervals. Often, an abrupt drop in user activity signals a broken frontend, a failing login service, or an API gateway issue. Instead of waiting for customers to complain, this automation alerts your engineering team instantly.

The workflow begins with a Schedule Trigger node set to run once every hour. Next, it routes execution to a Metabase node configured to execute a specific SQL question that counts active sessions within the last 60 minutes. The output payload is passed to an If node, which compares the returned DAU count against a defined critical threshold (for example, less than 150 active sessions).

If the session count falls below the limit, the workflow proceeds to the 'true' branch, where a Slack node posts a message to your internal alert channel. The message includes the current DAU count, the percentage change relative to the previous hour, and a direct hyperlink to the Metabase dashboard for further investigation.

Real-World Example

A SaaS platform experienced a sudden payment gateway failure that blocked new trial signups. Because their customer success team was offline, the issue went unnoticed for four hours.

By setting up this integration, they automated the detection process. The n8n schedule trigger ran an hourly SQL check:

SELECT count(distinct user_id) FROM user_sessions WHERE created_at >= NOW() - INTERVAL '1 hour';

When the query returned 12 users instead of the historical average of 80, the n8n logic node instantly identified the anomaly. It constructed a Slack block kit payload containing a warning emoji, the raw data, and a quick-action link, dispatching it to the engineering team's channel. Within minutes, engineers traced the issue back to a corrupted webhook endpoint, saving thousands of dollars in lost signups.

Workflow 2: Syncing Query Results to HubSpot

How It Works

Sales reps waste hours manually digging through business intelligence tools to figure out which leads are highly engaged. This workflow automates that process by extracting product usage metrics from Metabase and syncing them directly to your HubSpot CRM deals.

A Schedule Trigger fires once daily at midnight. An HTTP Request node performs a POST request to your Metabase API endpoint:

https://metabase.yourdomain.com/api/card/45/query

This retrieves a list of accounts that have performed more than 50 key actions in your app over the last seven days.

Once the JSON array of active companies is returned, an n8n Loop Over Items (or Split In Batches) node iterates through each record. For every record, a HubSpot node performs a lookup using the company's email domain. If a match is found, n8n updates a custom contact property named 'Weekly App Actions' and moves the corresponding deal to the 'Warm Leads' stage of your sales pipeline.

Real-World Example

Imagine an enterprise B2B sales team using HubSpot. They want to identify accounts that are using their collaboration tools heavily so they can upsell them to premium plans.

The Metabase query extracts the raw usage logs from the internal PostgreSQL database. n8n fetches this dataset, parsing the JSON elements:

  • company_domain: used to match the company in HubSpot.
  • active_users: mapped to a custom CRM field.
  • storage_used_gb: triggers a pipeline stage change if usage exceeds 500GB.

Instead of a sales representative manually querying SQL databases, n8n updates 150 accounts every morning, ensuring the sales team works with fresh, actionable data.

Pro Tips

To prevent API rate limits in HubSpot when syncing large datasets, configure the Wait node inside your loop. Setting a tiny delay of 200 milliseconds between each HubSpot update prevents your automation from getting blocked. Also, ensure you handle cases where Metabase returns empty results. Put an If node after your Metabase query to verify the array length is greater than zero before executing the loop; this saves processing memory and avoids execution errors.

Workflow 3: Weekly Executive PDF Report

How It Works

Executive stakeholders require high-level performance metrics, but they rarely log into BI platforms. This workflow generates a clean, automated PDF report combining multiple Metabase charts and emails it to the executive team every Monday morning.

A Schedule Trigger starts the execution at 8:00 AM on Monday. The workflow uses a series of HTTP Request nodes to download chart images directly from Metabase using its public or signed sharing URLs:

https://metabase.yourdomain.com/api/public/card/<uuid>/query/png

After downloading the PNG binary files, n8n routes them to an HTML to PDF community node or a customized Code node. This node structures the images into a clean, multi-page HTML template with professional CSS styles. Finally, the generated PDF binary is sent as an attachment via a Gmail or Resend node directly to your stakeholders.

Real-World Example

A logistics company needs to share a weekly delivery performance summary with their external board of directors. The board requires three specific charts: total shipments, average delivery time, and customer satisfaction scores.

Using n8n, the company configured three sequential HTTP requests to pull the latest weekly snapshots from their public Metabase dashboard. The binary data was consolidated into a single PDF document named 'Weekly_Performance_Report.pdf'. The output was dispatched to the board's distribution email list. This replaced a two-hour manual routine of taking screenshots, cropping them, pasting them into Google Slides, and exporting them as PDFs.

Workflow 4: Triggering ClickUp Tasks for Churn Risk

How It Works

Retaining existing customers is much more cost-effective than acquiring new ones. This proactive workflow alerts your Customer Success (CS) team the moment an account shows signs of churn risk based on declining system usage.

An SQL query in Metabase calculates a 'Churn Risk Score' for every account by looking at the ratio of usage over the last 14 days compared to the previous 30 days. If the score drops below 0.4, it indicates a 60% drop in platform activity.

A daily n8n workflow executes this Metabase question. The results are parsed, and for each account identified as high risk, n8n queries your application database to find the assigned account manager. It then uses the ClickUp node to create a high-priority task in the 'Customer Success' workspace. The task contains the customer's name, their current usage drop percentage, and a link to their historical usage logs.

Pro Tips

Avoid creating duplicate tasks for the same at-risk customer. Before adding a new task in ClickUp, use the ClickUp node's 'Get All Tasks' action filtered by the customer's unique identifier. Use an If node to check if an open task already exists. If one is found, update the task description with the latest telemetry rather than cluttering your workspace with duplicate tickets. This keeps your CS team's dashboard clean and focused.

Workflow 5: Giving an n8n AI Agent Direct Access to Metabase Dashboards

How It Works

Integrating generative AI with internal analytics transforms how teams consume data. Instead of having non-technical employees write SQL or ask analysts for simple metrics, you can create an n8n AI Agent that answers questions using your live Metabase dashboards.

The setup utilizes the AI Agent node in n8n, combined with an OpenAI Chat Model or a DeepSeek V4 model. You attach a Custom Tool to the agent called 'Query Metabase'. This tool is essentially a sub-workflow that takes a question ID as an input parameter.

When a user asks the AI Agent, 'How many signups did we have yesterday?', the agent identifies that it needs specific analytics. It calls the 'Query Metabase' tool with the corresponding Question ID. The sub-workflow executes the Metabase API call, parses the raw data into flat text, and returns it to the AI Agent. The agent then writes a natural, human-like summary of the numbers for the user.

Real-World Example

A retail company integrated this AI Agent into their internal Discord server. Store managers could query the bot directly: 'What were the top three selling products in Dallas yesterday?'

The n8n AI Agent decoded the intent, selected the Metabase lookup tool, and queried dashboard ID 89. It received a JSON payload listing items and sales volumes. The AI formatted the response into a bulleted list and posted it back to Discord within five seconds. This completely removed the barrier to data access for non-technical field managers.

Note: Executing complex queries via n8n triggers direct database read operations through Metabase. If you have hundreds of concurrent workflows running during peak business hours, your core database may experience significant CPU load. We recommend scheduling heavy reporting tasks during off-peak hours or connecting Metabase to a read-replica database to isolate analytical queries from transactional operations.

Why Use n8nautomation.cloud for Metabase Workflows?

Running sophisticated, high-frequency BI automations demands a stable and dedicated infrastructure. If you try to run these heavy workloads on shared public clouds, you will quickly hit rigid limits on execution timeouts, data transfers, and memory usage.

This is where n8nautomation.cloud stands out. Our managed, dedicated n8n hosting platform provides a reliable, secure environment tailored specifically for developers and business analysts who require maximum uptime and control. Here is why automated teams choose us:

  • Unbeatable Pricing and No Server Overhead: Starting at just $4/month, you get a fully managed, dedicated n8n instance. We handle all infrastructure, automatic backups, and server management so you can focus entirely on building workflows.
  • Complete Open-Source Freedom: Our platform runs the n8n Community Edition, giving you access to all 400+ built-in integrations, community nodes, and advanced triggers without arbitrary restrictions or paywalls.
  • Seamless Migration Tool: Already hosting your own n8n instance elsewhere? Our proprietary n8n migration tool lets you migrate your workflows within seconds. Simply provide the URLs and API keys for both your old and new (n8nautomation.cloud) instances, and we safely migrate your workflows. For security reasons, we only migrate the workflow definitions, allowing you to connect your credentials securely in your new dashboard.
  • Advanced Developer Features: Need to troubleshoot failing queries or audit API payloads? Our user dashboard provides real-time n8n logs, letting advanced users inspect errors instantly. Plus, we allow you to change your custom subdomain or domain anytime to match your corporate branding.

With automatic backups, instant setup, and 24/7 uptime, n8nautomation.cloud provides the most reliable foundation for running your Metabase and operational workflows. Check out our pricing plans today and set up your dedicated automation engine in seconds.

Ready to automate with n8n?

Get affordable managed n8n hosting with 24/7 support.