Sync data from
PlanetScale to Slack

Model your PlanetScale data using any of these methods

• dbt Model Selector

  

  Sync directly with your dbt models saved in a git.

• SQL Editor

  

  Create and Edit SQL from your browser. Hightouch supports SQL native to PlanetScale.

• Table Selector

  

  Select available tables and sheets from PlanetScale and sync using existing views without having to write SQL.

• Customer Studio

  

  For less technical users, pass traits and audiences from PlanetScale using our visual segmentation builder.

Why is it valuable to sync PlanetScale data to Slack?

Data platforms like PlanetScale are designed to help you consolidate all your data across your disparate data sources into a centralized platform so you can transform, model, and consume it through a dashboard or report.

The problem is that PlanetScale is typically only accessible to technical users who know how to write SQL, and dashboards are quickly forgotten; they don't help you take action on your data. You spend a lot of money getting your data into PlanetScale, so there's no reason for it just to sit there rotting away in a dashboard.

• Your customer success teams want to know when tickets come in and how to prioritize them
• Your sales team wants to know when a new user signs up and when an account's product usage exceeds your plan limits
• Your finance team wants to be notified when invoices are overdue, or payments fail

You need to take action on key events as they happen. However, gathering this information requires your business teams to hop back and forth between your various SaaS applications.

When you analyze your data in a dashboard, your business teams can only react. When you sync data from your warehouse to Slack, you enable your teams to be proactive. For example, a dashboard showing which customers have churned over the last six months is not very useful. However, if you notify your sales and customer success teams in Slack every time an account is at risk of churning, you can take action immediately.

Why should you use reverse ETL to connect PlanetScale and Slack data?

Many tools integrate with Slack, but not using your warehouse to power your notifications creates a complex web of point-to-point pipelines for every tool in your technology stack. In addition to this, you're limited to the data that exists within that platform, and in many cases, you need to join data from across your company to define specific events, and this is only possible in Snowflake.

When you leverage your Snowflake to power your notifications, you have the complete flexibility and familiarity of SQL. You can easily define your events and models and choose precisely how you want them to appear in Slack.

With Reverse ETL, you can customize your notification content in a single platform and choose how and where your messages appear. You can define complex notification triggers using SQL, and you can build interactive messages using powerful frameworks that you're already comfortable with. Hightouch even lets you take advantage of your existing data models. For example, if you have a lead scoring model in your warehouse, you can notify your sales reps once a specific lead reaches you and route it based to the appropriate person based on the criteria that you define.

Rather than building individual Slack messages in each of your tools and worrying about the consistency of your data, Hightouch lets you take advantage of the data that already exists in Snowflake and sync it to your destination in real time.

With reverse ETL, you can define everything in a single platform.