Overview
Metabase is an open-source business intelligence tool for creating dashboards and visualizations. The Flows360 Metabase connector allows you to automate administrative and data-related tasks within your Metabase instance.
Use workflows to programmatically manage your Metabase environment, including creating, updating, and syncing database connections. You can trigger table scans and card refreshes based on events in other applications, ensuring your analytics reflect the latest data.
This integration enables you to treat your BI platform as a dynamic component of your operational infrastructure. Connect CRMs, ERPs, and other data sources to Metabase to build fully automated, end-to-end data pipelines. Workflows can manage both the data flow and the analytics environment itself.
Capability summary
Authentication
Auth method: Metabase Session Token (API Key)
Required scopes
]
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Database | Yes | Yes | Represents a data source connection in Metabase. Supports create, update, and sync actions. |
| Table | Yes | No | Tables are managed via database schema syncs rather than direct manipulation. |
| Question / Card | Yes | No | A saved query in Metabase. Can be listed and executed. |
| Dashboard | Yes | Yes | A collection of questions (cards). Supports copy and modification actions. |
| Collection | Yes | Yes | A folder used to organize questions and dashboards. Supports creation and permission updates. |
| Pulse / Alert | Yes | Yes | A scheduled report or data-triggered alert. Supports creation. |
Supported actions
| Action | Description |
|---|---|
| list_databases | Retrieves a list of all database connections configured in the Metabase instance. |
| create_database | Creates a new database connection. |
| update_database | Updates the configuration of an existing database connection. |
| sync_database_schema | Forces Metabase to sync the schema for a specific database. |
| rescan_database_values | Forces Metabase to rescan the field values for a specific database. |
| run_card | Executes a saved question (card) and retrieves the results. |
| list_cards | Retrieves a list of all saved questions (cards). |
| create_collection | Creates a new collection to organize dashboards and questions. |
| add_question_to_dashboard | Adds an existing saved question (card) to a specific dashboard. |
| copy_dashboard | Creates a copy of an existing dashboard. |
| create_pulse_alert | Creates a new Pulse, which can be a scheduled report or an alert. |
| export_result_to_csv | Exports the results of a query or card to a CSV formatted string. |
| invoke_action_menu_item | Programmatically triggers an action from a Metabase Action Menu. |
| update_collection_permissions | Sets or updates the permissions for a specific collection. |
Setup steps
To connect to Metabase, you need to authenticate using a session token.
- Log in to Metabase: Sign in to your Metabase instance with a user account that has administrator privileges or sufficient permissions for the objects you intend to manage.
-
Generate a Session Token: Metabase does not use static API keys. You must programmatically request a session token by making a
POSTrequest to your Metabase instance's API endpoint/api/session.Example cURL Request:
curl -X POST -H "Content-Type: application/json" -d '{"username": "your-email@example.com", "password": "your-password"}' https://your-metabase-instance.com/api/session -
Extract the Token: The API will respond with a JSON object containing an
idfield. Thisidis your session token.Example Response:
{ "id": "a1b2c3d4-e5f6-7890-1234-567890abcdef" } - Configure the Connector: Copy the
idvalue from the response. In Flows360, create a new connection for Metabase. Paste the copied token into the API Key field and provide your Metabase instance URL (e.g.,https://your-metabase-instance.com).
Limitations
- The Metabase API uses a session token for authentication which expires. This token must be periodically regenerated and updated in the connection settings. The default session length is 14 days.
- API access and permissions are determined by the Metabase user account used to generate the session token. Ensure the user has the necessary administrative and data permissions for the intended operations.
- This connector is designed for administrative and operational tasks (e.g., managing connections, triggering syncs), not for executing arbitrary or complex data queries directly within a workflow. For data querying, use Metabase's native interface.