That dashboard you love only tells half the story until someone needs fresh data. Then come the permissions, tokens, and “who approved this” chaos. Metabase Pulsar exists to fix precisely that problem, turning scheduled queries into reliable, auditable messages instead of a pile of cron jobs that never aged gracefully.
Metabase is known for making business data readable. Pulsar, its event and scheduling layer, is what makes that readability continuous. It runs reports or alerts on a schedule, pushing results through channels like email, Slack, or webhook. In short, Pulsar makes your data proactive. Rather than a dashboard waiting for a click, it becomes a living broadcast of insight.
Integrating them sounds obvious, but the magic sits in the workflow. Pulsar needs to authenticate into Metabase, run parameterized queries, and deliver payloads to subscribers. Identity must be consistent across services or you risk the classic pain of mismatched permissions. Using OIDC or SAML with an identity provider such as Okta or AWS IAM gives you centralized access management. Roles map cleanly from query-level rights in Metabase to delivery privileges in Pulsar. That single source of truth is what keeps Pulsar’s automation both secure and transparent.
If you ever hit a snag, it usually comes down to RBAC alignment or stale credentials. Rotate Pulsar’s service tokens like you would any production secret, verify the connection uses scoped permissions, and review system logs when events drop. Pulsar’s logs are friendly enough to trace missed alerts without diving into the database itself.
Benefits at a glance