Twitter to Metabase Integration

How Datrise loads Twitter into Metabase

Datrise syncs Twitter's posts, users, engagement metrics, followers, mentions, and hashtags into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Twitter: Organic post activity and audience engagement on X.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Twitter entities map to Metabase

Twitter entity	Metabase object	Notes
posts	`twitter_posts`	id PK · custom fields → flattened columns for the question builder
users	`twitter_users`	id PK · linked to twitter_posts
engagement metrics	`twitter_engagement_metrics`	id PK · linked to twitter_posts
followers	`twitter_followers`	id PK · linked to twitter_posts

FAQ

How does Datrise handle Twitter's custom fields in Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the Twitter to Metabase sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Twitter to Metabase the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.