Metabase

Prerequisites

To set up Metabase you need:

• username and password - Credential pairs to authenticate with Metabase instance. This may be used to generate a new session_token if necessary. An email from Metabase may be sent to the owner's account everytime this is being used to open a new session.
• session_token - Credential token to authenticate requests sent to Metabase API. Usually expires after 14 days.
• instance_api_url - URL to interact with metabase instance API, that uses https.

Tables in the Metabase connector

No	Table Name	Columns	Primary Keys	Read Mode	Inc. Sync Keys	API Info
1	cards	25
2	activity	14	id	Full Refresh		API Reference
3	collections	11	id	Full Refresh		API Reference
4	dashboards	21
5	users	5	id	Full Refresh

Table: cards

No	Column Name	Type	Notes
1	result_metadata	VARCHAR
2	description	VARCHAR
3	created_at	VARCHAR
4	table_id	INTEGER
5	collection_id	INTEGER
6	archived	BOOLEAN
7	made_public_by_id	INTEGER
8	updated_at	VARCHAR
9	last-edit-info	VARCHAR
10	id	INTEGER
11	creator	VARCHAR
12	enable_embedding	BOOLEAN
13	dataset_query	VARCHAR
14	display	VARCHAR
15	embedding_params	VARCHAR
16	cache_ttl	INTEGER
17	query_type	VARCHAR
18	collection	VARCHAR
19	public_uuid	VARCHAR
20	visualization_settings	VARCHAR
21	collection_position	INTEGER
22	database_id	INTEGER
23	name	VARCHAR
24	creator_id	INTEGER
25	dataset	BOOLEAN

Table: activity

No	Column Name	Type	Notes
1	model_exists	BOOLEAN
2	custom_id	VARCHAR
3	model_id	INTEGER
4	table_id	INTEGER
5	database	VARCHAR
6	database_id	INTEGER
7	user_id	INTEGER
8	topic	VARCHAR
9	details	VARCHAR
10	model	VARCHAR
11	id	INTEGER	Primary Key
12	user	VARCHAR
13	table	VARCHAR
14	timestamp	VARCHAR

Table: collections

No	Column Name	Type	Notes
1	archived	BOOLEAN
2	color	VARCHAR
3	can_write	BOOLEAN
4	personal_owner_id	INTEGER
5	name	VARCHAR
6	namespace	VARCHAR
7	description	VARCHAR
8	authority_level	VARCHAR
9	location	VARCHAR
10	id	INTEGER	Primary Key
11	slug	VARCHAR

Table: dashboards

No	Column Name	Type	Notes
1	creator	VARCHAR
2	enable_embedding	BOOLEAN
3	description	VARCHAR
4	embedding_params	VARCHAR
5	cache_ttl	INTEGER
6	created_at	VARCHAR
7	caveats	VARCHAR
8	collection_id	INTEGER
9	archived	BOOLEAN
10	made_public_by_id	INTEGER
11	public_uuid	VARCHAR
12	collection_position	INTEGER
13	show_in_getting_started	BOOLEAN
14	updated_at	VARCHAR
15	last-edit-info	VARCHAR
16	name	VARCHAR
17	creator_id	INTEGER
18	points_of_interest	VARCHAR
19	id	INTEGER
20	position	VARCHAR
21	parameters	VARCHAR

Table: users

No	Column Name	Type	Notes
1	last_name	VARCHAR
2	id	INTEGER	Primary Key
3	common_name	VARCHAR
4	first_name	VARCHAR
5	email	VARCHAR

External Resources

• Metabase
• Card
• Dashboard
• User

Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.