ceven

Metabase

Runs complex data queries and pulls dashboard results into your workflows to trigger business actions based on live metrics.

Try Metabase in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Metabase integration

    • Describe the outcome and Ceven picks the right Metabase calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Metabase data, across all 189 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Metabase access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Metabase, when, and on whose behalf.
    • The agent pauses and asks when Metabase is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Metabase.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Metabase action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Metabase, and when to use it.

Run card query
Use this to execute the query linked to a specific card and pull the raw results into your workflow.
Run card pivot query
Pull results from a card formatted specifically as a pivot table for aggregation tasks.
Copy dashboard
Duplicate an existing dashboard to create a new version for a different collection or user.
Save dashboard to collection
Create a new dashboard directly inside a specific collection with full configuration.
Trigger database schema sync
Force Metabase to update its metadata when you change tables or columns in your database.
Trigger field values rescan
Refresh the list of available values for filter dropdowns after data updates.
Sync table schema
Update the schema metadata for one specific table to reflect recent database changes.
Search dataset parameters
Find valid parameter values for cards or dashboards to use as inputs for queries.
Delete API cache
Clear cached data for a specific dashboard or question to ensure you see the most recent data.
Create bookmark
Save a specific card or dashboard for the authenticated user for faster access.
Update field values
Manually set human readable values for category or boolean fields in the data model.
Delete dashboard
Permanently remove a dashboard and its associated configuration from the system.
Run Dashboard Pivot DashCard Query
Tool to run a pivot table query for a specific DashCard. Use when you need to execute a pivot table query on a dashboard card with optional parameter filters.
Discard Database Field Values
Tool to discard all saved field values for a specific database. Use when you need to clear cached field value data for all fields in a database. Requires superuser privileges.
Dismiss Database Sync Spinner
Tool to manually set the initial sync status of a Database and corresponding tables to complete. Use when you need to dismiss the synchronization spinner for a database after initial setup.
Trigger Database Field Values Rescan
Tool to trigger a manual scan of field values for a Database. Use when you need to refresh field values for filter dropdowns after data changes. Requires superuser permissions.
Search Dataset Parameter Values
Tool to search for parameter values in datasets when editing cards or dashboards. Use when you need to provide autocomplete functionality for parameters. Expects a query string and returns matching values.
Create Field Dimension
Tool to set the dimension for a field at the specified ID in Metabase. Use when you need to configure field remapping or display values for better data presentation.
Discard Field Values
Tool to discard the FieldValues belonging to a Metabase field. Use when you need to clear cached field values. Only applies to fields that have FieldValues. If the Field's Database is set up to automatically sync FieldValues, they will be r
Unpersist Card
Tool to unpersist a Metabase card/model. Deletes the persisted table backing the model and all queries after this will use the card's query rather than the saved version. Use when you need to remove persistence from a model.
Disable Database Model Persistence
Tool to disable model persistence for a Metabase database. Use when you need to turn off caching of model results. Returns success whether persistence was already disabled or not (idempotent operation).
Discard Table Field Values
Tool to discard the FieldValues belonging to the Fields in a Metabase Table. Use when you need to clear cached field values for all fields in a table. Only applies to fields that have FieldValues. If this Table's Database is set up to autom
Rescan Table Field Values
Tool to manually trigger an update for FieldValues for Fields belonging to a specific Table. Use when you need to refresh field value caches after table data changes. Only applies to Fields that are eligible for FieldValues.
Delete Action
Tool to delete an Action from Metabase. Use when you need to permanently remove an action. This operation cannot be undone.
Delete Bookmark
Tool to delete a bookmark from a Metabase item (card, dashboard, or collection). Use when you need to remove a bookmark from a specific item.
Delete Card
Tool to delete a Metabase card (question) by its ID. Use when you need to permanently remove a card. Note: This endpoint is deprecated - consider archiving cards instead.
Delete Model Index
Tool to delete a Metabase model index by its ID. Use when you need to permanently remove a model index entry.
Delete Timeline Event
Tool to delete a timeline event by ID. Use when you need to permanently remove a specific timeline event from Metabase.
Delete Timeline
Tool to delete a timeline by ID. Use when you need to permanently remove a timeline. Returns success status on completion.
Delete User Key Value
Tool to delete a user key value pair from Metabase. Use when you need to remove a stored key value entry within a specific namespace.

30 actions · scroll to see them all

Frequently asked questions

Ceven operates using the permissions of the user account connected via the API. If the connected user does not have access to a specific collection or database in Metabase, the agent will receive a 403 forbidden error and cannot pull that data. We recommend creating a dedicated service account in Metabase with read only access to the specific collections required for your workflows. This ensures that the agent cannot accidentally modify sensitive data models or delete critical dashboards while still having enough access to run the necessary queries for your automation.
Ceven focuses on executing and managing existing assets. It can run card queries and copy dashboards, but it does not currently build new SQL questions from scratch. You should define your core business logic as a Card or Model within the Metabase UI first. Once the card exists, Ceven can run it on a schedule, pass parameters into it, and use the output to trigger other apps. This approach keeps your data logic centralized in Metabase where it can be audited by your data analysts before being used in a live workflow.
Metabase caches field values to keep filter dropdowns fast. If you have recently added new data to your database, those values might not appear in the search parameters immediately. You can solve this by using the Trigger Database Field Values Rescan action. This forces Metabase to scan the columns again and update the cache. Depending on the size of your table, this can take a few minutes. We suggest adding a rescan step to your workflow if you rely on dynamic filter values that change daily.
Metabase has internal limits on the size of result sets returned via the API to prevent system crashes. If a card returns hundreds of thousands of rows, the API may truncate the results or timeout. For very large datasets, we recommend refining the card query in Metabase to use more restrictive filters or aggregation. If you need to process massive amounts of raw data, it is better to use a database connection directly rather than routing through the Metabase visualization layer, as the API is optimized for dashboard sized results.
Yes, Ceven works with both the open source and Enterprise versions of Metabase. If you are using Enterprise features like fine grained access control or auditing, the agent will respect those settings based on the API token used. However, some advanced embedding features may require specific configuration in your Metabase admin panel to allow external API calls from our servers. If you encounter permission errors despite having the correct role, check your SSO and session settings in the Metabase admin console to ensure API access is enabled.
Yes, you can use the Sync Table Schema or Trigger Database Schema Sync actions. This is particularly useful if you have a data pipeline that adds new columns to your warehouse on a schedule. Instead of manually clicking sync in the Metabase admin panel, you can build a Ceven workflow that triggers the sync immediately after your ETL job finishes. This ensures that your dashboards and agents always have the latest schema metadata without any manual intervention or downtime in your reporting.
Metabase caches query results to improve performance. Sometimes this means an agent pulls data that is a few minutes old. Use the Delete API Cache action to invalidate the cache for a specific entity. This forces Metabase to run a fresh query against your database the next time the card is accessed. This is critical for high stakes workflows where you need second by second accuracy. Be mindful that clearing the cache frequently for very heavy queries can put additional load on your underlying data warehouse.
If a card used in a Ceven workflow is deleted or archived, any action attempting to run that card will fail with a 404 not found error. The workflow will stop at that step and trigger your configured error handling. To prevent this, we recommend using a naming convention for cards used in automation and placing them in a protected collection where only admins have delete permissions. This prevents accidental deletions from breaking your production data pipelines and ensures your operational automations remain stable.

Alternatives to Metabase

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Tableau logoTableauLooker logoLookerPower BI logoPower BISigma logoSigma

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Metabase and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free