METABASE n8n INTEGRATION: AUTOMATE METABASE WITH N8N

This action fetches the actual data results from a specific Metabase question (saved query) and returns them in your preferred format. It's the cornerstone of any reporting automation—when you need fresh data from your dashboards delivered somewhere else, this is your go-to action.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials for authentication (required)
• Resource: Set to "Question" to indicate you're working with saved queries
• Operation: Set to "Result Data" to fetch the actual query results
• Question ID: Numeric identifier of the specific Metabase question to retrieve data from (required)
• Format: Dropdown to select output format—CSV is shown in the example, perfect for spreadsheet integrations

Use cases:

• Export daily sales reports to Google Sheets automatically every morning
• Feed fresh analytics data into Slack channels for team visibility
• Populate external dashboards or data warehouses with Metabase query results

This action retrieves multiple questions (saved queries) from your Metabase instance in a single operation. It's particularly useful when you need to audit your BI environment, sync question metadata to external systems, or build dynamic workflows that adapt based on available queries.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Question" to target saved queries in Metabase
• Operation: Set to "Get Many" to fetch multiple question records at once

Use cases:

• Create an inventory of all saved questions for documentation purposes
• Build workflows that dynamically process multiple reports in sequence
• Sync question metadata to project management tools for better BI governance

This action retrieves detailed information about a single specific question by its unique identifier. Use it when you need metadata about a particular saved query—its configuration, last run time, creator, or other properties.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Question" to work with saved queries
• Operation: Set to "Get" to fetch a single question's details
• Question ID: Numeric or text field where you specify the exact question to retrieve (required)—can be a fixed value or dynamic expression

Use cases:

• Verify a question exists before attempting to fetch its results
• Retrieve question metadata to include in automated reports
• Build conditional workflows that behave differently based on question properties

This action fetches multiple metrics from your Metabase instance at once. Metrics in Metabase are reusable calculations that maintain consistency across your organization—retrieving them programmatically helps maintain data governance.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Metric" to interact with Metabase metrics
• Operation: Set to "Get Many" to retrieve multiple metric definitions

Use cases:

• Audit all defined metrics for consistency and documentation
• Sync metric definitions to external data catalogs
• Build monitoring workflows that track metric changes over time

This action retrieves detailed information about a single metric by its unique identifier. Perfect for workflows that need specific metric metadata or validation before using that metric in calculations.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Metric" to work with Metabase metrics
• Operation: Set to "Get" to fetch a single metric's details
• Metric ID: Numeric field where you provide the unique identifier of the metric to retrieve (required)

Use cases:

• Validate metric configurations before running dependent reports
• Include metric definitions in automated documentation workflows
• Monitor specific high-value metrics for configuration changes

This action retrieves all fields (columns) from a specific database connected to your Metabase instance. It's essential for understanding your data structure and building dynamic queries or data mapping workflows.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Database" to interact with database resources
• Operation: Set to "Get Fields" to fetch the field/column structure
• Database ID: Numeric field specifying which database to retrieve fields from (required)

Use cases:

• Document database schemas automatically for data dictionaries
• Build dynamic workflows that adapt to changing table structures
• Validate that expected fields exist before running data pipelines

This action retrieves multiple database connection records from your Metabase instance. Use it to audit your connected data sources or build workflows that interact with multiple databases.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Database" to work with database connections
• Operation: Set to "Get Many" to fetch multiple database records
• Simplify: Toggle switch to return data in a simplified, easier-to-process format (optional but recommended)

Use cases:

• Create an inventory of all database connections for security audits
• Monitor database connection health across your Metabase instance
• Build workflows that process data from multiple sources in sequence

This action programmatically adds a new database connection to your Metabase instance. It's particularly valuable for DevOps workflows, automated environment provisioning, or scaling scenarios where databases are created dynamically.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Database" to manage database connections
• Operation: Set to "Add" to create a new database connection
• Engine: Dropdown to select the database type (PostgreSQL, MySQL, etc.)
• Host: Text field for the database server hostname/IP and optional port
• Name: Text field for the display name in Metabase
• Port: Numeric field for the database connection port
• User: Text field for the database username
• Password: Text field for the database user's password
• Database Name: Text field for the actual database name to connect to

Use cases:

• Automatically provision Metabase connections when new databases are created
• Build self-service workflows where teams can request new data source connections
• Sync database connections across multiple Metabase environments

This action retrieves multiple alerts configured in your Metabase instance. Alerts in Metabase trigger when query results meet certain conditions—fetching them programmatically enables sophisticated monitoring workflows.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Alert" to work with Metabase alerts
• Operation: Set to "Get Many" to fetch multiple alert records

Use cases:

• Audit all configured alerts for compliance and coverage
• Build meta-monitoring that tracks alert configurations across your instance
• Sync alert definitions to external incident management systems

This action retrieves detailed information about a single alert by its unique identifier. Use it when you need to verify alert configuration, check status, or route specific alert information to other systems.

Key parameters:

• Credential to connect with: Dropdown to select your Metabase account credentials (required)
• Resource: Set to "Alert" to interact with Metabase alerts
• Operation: Set to "Get" to fetch a single alert's details
• Alert ID: Numeric field where you provide the unique identifier of the alert to retrieve (required)

Use cases:

• Verify alert configurations before critical business periods
• Include alert details in automated status reports
• Build conditional workflows that respond differently based on alert properties