Picture this: your team needs analytics data from Metabase, but every query triggers a new approval, a new token, and another Slack ping. The dashboards are gorgeous, the process is not. That’s where Conductor Metabase comes in—pairing orchestration and analytics so teams can run data workflows with reliable, identity-aware access.
Conductor acts as the control plane. It handles workflow automation, service tasks, and access logic. Metabase handles the visualization and exploration side, giving your stakeholders the colorful charts they crave. Together they create a loop of data clarity and operational discipline. The integration works best when you treat access control as part of the pipeline instead of an afterthought.
At the core, Conductor Metabase integration hinges on two ideas: authenticated orchestration and auditable visualization. Conductor kicks off a workflow, calls Metabase through a secure identity proxy, and ensures every dashboard run is tied to a verified identity. The goal is simple: no static credentials, no shared secrets, no late-night token rotations.
To wire the two systems together, map your identity provider—something like Okta or AWS IAM—by issuing scoped tokens only for workflow service accounts. Conductor reads these through environment variables or secret stores, then generates signed requests to Metabase’s API or embeds them in dashboard automation jobs. Permissions stay bound to the workflow definition, not the human. This prevents stale privileges and keeps SOC 2 auditors happy.
If something fails, it’s usually a permissions mismatch. Check that the Conductor workflow service account has the right Metabase group membership. Rotate keys regularly. Use OIDC where possible. These basic hygiene steps solve 90 percent of "it works locally but not in CI" mysteries.